
ix3ht (ix3ht) asked a question.
Hi. I've installed another Okta IWA agent but am having issues with our wildcard certificate on IIS 8.5. The cert is valid but when I type in the URL of the agent I get a NET::ERR_CERT_COMMON_NAME_INVALID error.
I'm not sure why this would be as theoretically the URL of the agent is covered by the cert. Any advice would be appreciated.

What is the common name of the cert - *.domain.com?
Hi Jeff. Yes, that's correct.
Does your IWA server have the same domain suffix as your wildcard cert, i.e. cert=*.domain.com and iwa=servername.domain.com?
Yes it does
I assume you bound https/443 to the wildcard cert in IIS? I'm also going to assume the other IWA is IIS 8.5. Did you restart the app pool or the website? What do the logs on new IWA server?
The other IWA agent is running IIS 10 - I did bind the WC cert correctly on the new agent. In terms of the logs, I just see various GET/POST entries
what happens if you go to https://servername.domain.com? Do you get the same error? If not, I would suggest either opening a case with support or reinstalling the IWA.
If I go to the server URL I get taken to the IIS page - it does say 'Not Secure' but there's no choice to view a certificate. If I add IWA to the end of the URL I can see it says Not Secure but it quickly redirects to the main login page. All very strange. I'll see how I get on with support. Thanks a lot for the help!
Since the IIS page says Not Secure, it sounds like an issue with the cert or the way it was installed. I would revisit that first... Also, do you see the cert correctly in Certificate Manger in the MMC, including the private key?
You can try adding *.domain.com to both the CN and SAN section of the cert.