mkcert: IIS complains about missing intermediates
Hi,
- Windows 10 1809 Professional
- IIS 10.0.17763.1
- Have run mkcert -install
Generated my new wildcard certificate as:
mkcert -pkcs12 "*.ozc.black"
I then go to IIS > Server Certificates and try and import it but am prompted for a password?
What am I missing here? It is not my login password.
About this issue
- Original URL
- State: open
- Created 5 years ago
- Comments: 16 (4 by maintainers)
Installing on Trusted Root CA folder (In MMC) solved the issue !
After installing the generated localhost.pfx certificate, IIS doesn’t give the warning message anymore, and .NET Core also trust the certificate.
It looks like the Subject Alternate Name for the certificate in IIS is “2021-06-24.localtest.me” whereas the binding is localhost which is causing a mismatch preventing the .Net Core application from trusting the certificate The moment i solve the IIS error, it gives me the name mismatch, but generating again the certificate for localhost solved the problem
I’m afraid we have to wait for someone who actually dealt with IIS, I have never actually used it.