|
From http://en.wikipedia.org/wiki/PKCS_%E2%99%AF12
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Versfelt, Charles
Sent: Tuesday, September 10, 2013 2:05 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Certificate authentication through HTTPS
Brad,
Thank you for the explanation! I definitely needed that background for
better understanding.
Now... I found out some more information that may shed light on my
problem.
I tried sending my CSV send again and again failed with the handshake error.
I wanted to try creating an application through the DCM and do it that way.
Bruce (he's the Operations VP) sent me a "Goto meeting" and we went
through the screens together.
During the process, I asked about the final certificate, a .p12 file. He told me
that, while he was unable to load the .p12, he was able to "launch" the .p12
and turn it into a .cer!
This doesn't sound right to me. I suspect my problem is because we never
loaded the .p12 in its correct form.
Am I right, and if so, is there anything different he needs to do to load a .p12
certificate on the AS/400?
Thanks,
Charlie
PS. No, using the named application didn't work either. Handshake error.
This email message has been delivered safely and archived online by
Mimecast. For more information please visit http://www.mimecast.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 mailing list archive is Copyright 1997-2025 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.