Re: Self-Signed Certificates For PayPal And HTTPAPI

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

Hi Anthony,

Self-signed certificate can mean two different things:

1) Creating certificates where you act as your own CA.  You sign the 
certificates yourself, so you refer to it as "self-signed".

2) A certificate what lists itself as it's own CA.  Thus the certificate 
is signed by itself, or "self-signed".

AFIAK, IBM i does not support option #2.  And please understand that 
HTTPAPI doesn't know anything about certificates -- it lets IBM i (aka 
OS/400) handle all of that stuff.  So if IBM i doesn't support them, 
HTTPAPI won't work with them.

Option #1 should work just fine, though.  In fact, the system comes with 
a "Local CA" built in to the DCM to make it easy to create these sorts 
of certs.  (Easier, in fact, than it is on any other platform I've 
worked with!)

If you're working with option #1 and you're stuck, please let us know 
where you're stuck.


On 7/13/2010 3:12 PM, Anthony_Wilson@xxxxxxxxxxxxxxx wrote:
>
> We are attempting to connect directly with PayPal using their SOAP APIs.
> The coding is working when we provide a username / password based call but
> we have been asked for our final product to utilize a self-signed
> certificate
>
> We could use a little help / direction on how this is accomplished.  Do we
> still load the self-signed certificate into the digital certificate
> manager?  We are having problems doing this.  Does anyone have a link to
> instructions or perhaps notes where you have done this yourself?
>
> Thanks everyone for any assistance.
>
> Anthony Wilson
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------