×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Well, the common name is probably invalid 🙂
If they have the same cert on both LPARs, well, each LPAR has its own name.
So on one or the other LPAR the name is invalid.
________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
Sent: Tuesday, June 18, 2024 11:56 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: self signed certs and api calls
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
So we have an off platform gui application that calls a rest api on the IBM
i.
On one lpar, the api is consumed fine with no certificate error.
On the other lpar, the api is consumed and we see in developer tools...
net::ERR_CERT_COMMON_NAME_INVALID
However the cert on both lpars is the same cert.
what could be going on here?
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.
midrange.com
