How to Resolve when "IWA authenticated.aspx" Page Shows the Error: "Not Secure"
Last Updated:
Okta Classic Engine
Directories
Overview
This article provides a solution for an issue where the Integrated Windows Authentication (IWA) authenticated.aspx page displays the following error.
Not Secure
Applies To
- Okta IWA
- SSL CSR
- Desktop Single Sign-On (DSSO)
- Okta Classic Engine
Cause
The error occurs due to an incorrect configuration of the SSL (Secure Sockets Layer) certificate on the client server's side.
The Common Name specified in the SSL certificate does not match the client IWA FQDN or hostname, or the wildcard cert name in the URL.
Solution
To resolve this issue, the Secure Sockets Layer (SSL) certificate must be recreated with the correct IWA FQDN hostname OR the wildcard cert.
- Recreate the SSL certificate using the IWA FQDN hostname OR the wildcard URL (for example, <IWAhostname.domain.com>) as the Common Name.
- Alternatively, specify the IWA FQDN hostname OR the wildcard URL in the Certificate Subject Alternative Name section.
