× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.






Hey, that was it!!!  I had the client certificate set as trusted but not
the CA.  Thanks Brad!

Dave Parnin
Nishikawa Standard Company
Topeka, IN  46571
daparnin@xxxxxxxxxxxxxxxxxx




                                                                                
                                 
                      Brad Stone                                                
                                 
                      <brad@xxxxxxxxxxxx>         To:       Midrange Systems 
Technical Discussion                
                      Sent by:                     
<midrange-l@xxxxxxxxxxxx>@SMTP@CTB                            
                      midrange-l-bounces@m        cc:       (bcc: David A 
Parnin/Topeka/NISCO/SPCO)              
                      idrange.com                 Subject:  Re: HTTP API 
Certificate Error ???                   
                                                                                
                                 
                                                                                
                                 
                      07/29/2004 10:00 AM                                       
                                 
                      Please respond to                                         
                                 
                      Midrange Systems                                          
                                 
                      Technical Discussion                                      
                                 
                      <midrange-l@midrange                                      
                                 
                      .com>                                                     
                                 
                                                                                
                                 
                                                                                
                                 



You should be able to take the cert you received from the
bank and view who it is signed by, then make sure you have
the proper CA installed on your AS/400.

Usually double clicking on a certificate will show that.

You can also use DCM to view the cert's details, like the
signer, etc.

The problem is most likely that the cert is signed by a CA
you don't "trust" or have on your As/400.

Brad

On Wed, 28 Jul 2004 16:57:04 -0500
 daparnin@xxxxxxxxxxxxxxxxxx wrote:
>
>
>
>
> I'm trying to implement Scott Klement's HTTPAPI code but
> am having a
> problem that appears to be that looks to me like the
> digital certificate
> isn't being used.  I'm getting the following message from
> Scott's API:
>
> SSL Handshake: (GSKit) Certificate is not signed by
>
> Is this a problem with the certificate set up in the
> Digital Certificate
> Manager?  The name of the client certificate should be
> "nkausrf1".  I have
> been able to install the same certificate on my PC and it
> works fine for
> accessing the web page and doing file transfers.  The
> client signing
> certificate that is being used on my PC has the same
> serial# as the one in
> the DCM.
>
> I should point out that IBM supplied me with the CA and
> Root certificates
> because the bank that supplied the client certificate
> couldn't seem to give
> me the CA certificate or tell me who issued it.  I
> suppose that I could
> export the CA and Root certificates from my PC and try to
> import them to
> the DCM but should that be necessary?  Would it do any
> good?
>
> Dave Parnin
> Nishikawa Standard Company
> Topeka, IN  46571
> daparnin@xxxxxxxxxxxxxxxxxx
>
> --
> This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit:
> http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the
> archives
> at http://archive.midrange.com/midrange-l.
>

Bradley V. Stone
BVS.Tools
www.bvstools.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.