One assumes you are creating your certificate chain yourself.
With self-signing, there's a difference between the cert being self-signed, and the cert being signed by a self-created CA cert.
Are you sure you've been consistent over the years, which ever way you are doing it?
*
If the new cert itself is self-signed, then use the iACS Key Management Tool to import it.
*
If your new cert is signed by your self-created CA cert, and that was already in use, this should be working and we'll need to look at it more deeply.
Jack Woehr
Independent Consulting Programmer
303-847-8442
jack.woehr@xxxxxxxxxxx
www.procern.com
Stay Connected!
New Name. Same Great Service.
NON-DISCLOSURE NOTICE: This communication including any and all attachments is for the intended recipient(s) only and may contain confidential and privileged information. If you are not the intended recipient of this communication, any disclosure, copying further distribution or use of this communication is prohibited. If you received this communication in error, please contact the sender and delete/destroy all copies of this communication immediately.
________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of Sizer, Joseph via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>
Sent: Friday, March 1, 2024 7:50 AM
To: 'midrange-l@xxxxxxxxxxxxxxxxxx' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Sizer, Joseph <JSizer@xxxxxxxxxx>
Subject: TLS/SSL Certificate update for IBM i ODBC
The error message generated when testing the connection is:
Data link error: Test connection failed because of an error in initializing provider. IBM System I Access ODBC Driver Communication link failure. Comm rc-25414 - CWBCO1050 - The IBM I server application certificate is not trusted.
As an Amazon Associate we earn from qualifying purchases.
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.