IIS 7 and Above
IIS 10 and wildcard certificates
Last post Aug 05, 2020 08:45 AM by Yuk Ding
Jul 30, 2020 06:14 PM|MissAmberClark|LINK
I'm trying to set up HTTPS on an internal website where I work. It is one of many sites on the webserver. The certificate comes from an internal certificate authority and is a wild card certificate (*.mycompany.com).
When accessing the site (https://app.mycompany.com) I get the following certificate error ERR_CERT_COMMON_NAME_INVALID.
The web site has the following bindings:
Jul 30, 2020 10:07 PM|lextm|LINK
I doubt if you have mapped the right certificate, but SSL Diag should reveal that,
Run a report and see what it says.
Jul 31, 2020 07:08 AM|Yuk Ding|LINK
What error message did you see if you open the website in chrome and go to security tab? It should show the root cause. Please ensure the wildcard certificate is also valid for client side. I mean the client also trust your internal certificate chain.
Please ensure you have register the authority and certificate chain correctly.
Jul 31, 2020 04:39 PM|MissAmberClark|LINK
@lextm recommended the SSLDiag and that was helpful. SSLDiag showed that everything was set up correctly.
Since it looked okay, I tried the site in IE11 and Edge. Both of those browsers worked and did not show any certificate errors.
Since Chrome is not trusting the cert, but the Microsoft products are, I'm thinking that IE and Edge trust the cert because the CA can be found in the AD domain, whereas Chrome does not. Well, that's my theory, anyway.
Aug 05, 2020 08:45 AM|Yuk Ding|LINK
Chrome has its independent standard to verify certificate. So please check your chrome developer tool to show the real error message.