Re: self signed certs and api calls

James, your understanding is correct...

Subject Alternative Name (we have a customer who does something like

that for a webapp).

on the lpar we do not have an issue with, the alternative name also has the
same info (URL) as the common name.
So on the problem lpar cert, we tried applying the same common name to the
alternative name also... but no luck in resolving the issue.

thanks

Jay

On Tue, Jun 18, 2024 at 3:20 PM James H. H. Lampert via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

On 6/18/24 11:14 AM, Jay Vaughn wrote:

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

I haven't been following this thread, but . . .

My understanding is that you're hosting a web service on 2 different
LPARs, using a common certificate for HTTPS.

It seems to me that in a case like that, I'd expect the application
that's accessing the web service to be going to some common URL, e.g., a
load-balancer. In that case, you'd want the cert to have the
load-balancer's URL.

Or if your consumer really is specifically accessing the service on a
particular LPAR, then you should probably have every supported URL for
your service listed on the cert as a Subject Alternative Name (we have a
customer who does something like that for a webapp).

Just my thoughts on the subject. Maybe useful, maybe not.

--
JHHL

--
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.