Re: self signed certs and api calls

[Jay Vaughn <jeffersonvaughn@xxxxxxxxx>]

funny thing... the lpar that is giving us the error the common name looks
right on it...
and the lpar that does not give the issue, the common name looks nothing
like the identification of that lpar

???

Jay

On Tue, Jun 18, 2024 at 2:05 PM Jack Woehr via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

> 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?
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.