Re: Self-Signed Certificates For PayPal And HTTPAPI

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

Hi Anthony,

That link points to a solution for what I previously referred to as #1 
from a Java program.  Thus, if you are using #2 (as you state) then that 
solution won't help you.  If you are indeed using #1, then that solution 
would help you in Java -- or there's a much easier way in RPG.

Please start by telling us whether you have a single certificate that 
acts both as a CA cert and a client cert (i.e. situation #2), or whether 
you have separate CA cert and client cert (situation #1)

Because the separate CA/client cert issue is one we can explain to you.



On 7/13/2010 3:58 PM, Anthony_Wilson@xxxxxxxxxxxxxxx wrote:
> Scott,
>
> Thank you for your quick response.  I believe we are trying to do option
> #2.  Sweet biscuits - this is not good news!
>
> We were poking around the IBM website and found this link on self-signed
> certificates.  Is there something in this that might assist me?  I think
> this is Java work here, which may keep us from being able to use HTTPAPI.
>
> http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/rzahh/sslcert.htm
>
> Thanks again.
>
> Anthony Wilson
> Direct To Consumer Analyst
> Abercrombie&  Fitch
> Direct:  614.765.4807
> Email:  anthony_wilson@xxxxxxxxxxxxxxx
>
>
>
>
>    From:       Scott Klement<sk@xxxxxxxxxxxxxxxx>
>
>    To:         HTTPAPI and FTPAPI Projects<ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
>
>    Date:       07/13/2010 04:40 PM
>
>    Subject:    Re: Self-Signed Certificates For PayPal And HTTPAPI
>
>
>
>
>
>
> 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
> -----------------------------------------------------------------------
>
>
>
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list.  To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------
>

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------