Wait, you got a wildcard cert onto your HMC? We need to talk.How did you do that?

But to answer your question I believe *.dekko.com should indeed work for hmc02.corp.dekko.com.

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 12/13/2017 9:48 AM, Rob Berendt wrote:
Suppose your external addresses are something like
myserver.mycorp.com
and your internal addresses are something like
myserver.corp.mycorp.com
Then is a wildcard certificate for *.mycorp.com would work for
myserver.mycorp.com but not myserver.corp.mycorp.com, right?

The reason I am asking is that I have this ticket open with IBM regarding
putting a valid cert on my HMC and their reply is:
<snip>
After reviewing the logs again, I noticed that the certificate you have
installed is for *.dekko.com, but you are hitting the HMC using
"https://hmc02.corp.dekko.com"; which is a different domain and likely
what is causing the browser to complain.
</snip>

Rob Berendt


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.