I loaded the full chain .pfx file to DCM and then loaded just the intermediate to IBM i Access, IIRC. I didn't export it from DCM either, I exported a .cer from my windows certificate store as that's faster than working with DCM which I consider painfully slow.
Coy Krill
Core Processing Administrator/Analyst
Washington Trust Bank
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Friday, January 30, 2015 13:10
To: 'Midrange Systems Technical Discussion'
Subject: RE: iSeries Access for Windows PC sessions SSL cert issue
Importance: Low
Cory,
Thanks for info.
Your SSL almost dittos ours.
We just renewed our Geo wildcard cert, from SHA1 to SHA256.
I'm still researching an issue with our new SHA256 cert It was given to me as a .pfx file, which I imported to DCM ok.
I then had to export the root from DCM for iSeries Access for my PC.
The root that I exported from DCM displays issued to and by: Equifax Secure Certificate Authority Everything is working, but this cert is showing some strange characteristics.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Krill, Coy
Sent: Friday, January 30, 2015 3:51 PM
To: Midrange Systems Technical Discussion
Subject: RE: iSeries Access for Windows PC sessions SSL cert issue
Security Protocol: TLS 1.0
Security Encryption Level TLS_RSA_WITH_AES_128_CBC_SHA Server Certificate Information: *.wtdomain.com
Our wildcard cert is issued by GeoTrust SSL CA - G3 under GeoTrust Global CA.
Since we use it for most everything it's in the windows certificate store and the the IBM i Access certificate store.
Ours also says "All the intended purposes of this certicate could not be verified" but it causes no issues. I believe that's because it's not just a wildcard from a server perspective but also from a service perspective.
Coy Krill
Core Processing Administrator/Analyst
Washington Trust Bank
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Friday, January 30, 2015 12:13
To: 'Midrange Systems Technical Discussion'
Subject: iSeries Access for Windows PC sessions SSL cert issue
Importance: Low
Anyone using SSL to secure iSeries Access for Windows on your PC sessions.
What does your, Communication, Security Information, Connection, View Certificate tab look like.
Even though SSL is working and verify all states ok, I'm seeing this.
All the intended purposes of the certificate could not be verified.
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx<mailto:psteinmetz@xxxxxxxxxx>
http://www.pencor.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.
=====================================================================================================
This electronic mail message and any attachments may contain confidential or privileged information and is intended for use solely by the above-referenced recipient. Any review, copying, printing, disclosure, distribution, or other use by any other person or entity is strictly prohibited under applicable law. If you are not the named recipient, or believe you have received this message in error, please immediately notify the sender by replying to this message and delete the copy you received. =====================================================================================================
--
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.
--
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.
=====================================================================================================
This electronic mail message and any attachments may contain confidential or privileged
information and is intended for use solely by the above-referenced recipient. Any review,
copying, printing, disclosure, distribution, or other use by any other person or entity is
strictly prohibited under applicable law. If you are not the named recipient, or believe
you have received this message in error, please immediately notify the sender by replying
to this message and delete the copy you received. =====================================================================================================
midrange.com
