self signed certs and api calls -- MIDRANGE-L

Subject: self signed certs and api calls
From: Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
Date: Tue, 18 Jun 2024 13:56:33 -0400
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

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?

tia

jay

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: self signed certs and api calls , Jack Woehr
Re: self signed certs and api calls , Scott Klement

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.