This article covers the intriguing scenario in which a QR code generated during the Okta Verify setup on an Okta subdomain redirects to a custom domain.
- Okta Verify
- Okta Identity Engine (OIE)
- Okta Classic Engine
During the Okta Verify setup process, the QR code generated on an Okta subdomain (for example, <example>.okta.com) actually points to a custom domain. As a result, the Okta Verify app displays the URL of the custom domain, not the Okta subdomain.
The described behavior is anticipated. When accessing the standard Okta URL to enroll an account in Okta Verify, the custom domain will be presented because of the associated brand for that specific tenant. This behavior remains consistent across both Okta Classic Engine and Okta Identity Engine (OIE).
NOTE: If two custom domains are associated with the Okta tenant, the URL of the Okta default subdomain will be displayed.
