Okta Custom Domain - Https Not Secure

Okta custom domain was setup successfully. The authorization server is updated to use the custom domain as the issuer. The web application is now going through the custom domain for authentication which is successfully in desktop but not in the mobile like iphone, and I suspect it’s because the https not secure issue.

By Okta, the not secure is supposed to be cleared up in 48 hours after the custom domain is setup? In my case, it has been passed that window.

So my question is how to facilitate the certificate propagation on Okta’s side? Are there any way to request that?

here is the output from ssl checker: I am getting common names doesn’t match

Did you provide your own certificate for your domain? If so, I’d open a ticket with Okta support to investigate, why it was not applied

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.