<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
Adding an Account in Okta Verify When Having a Custom Domain
Okta Identity Engine
All Engines
Okta Classic Engine
Multi-Factor Authentication
Overview

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.

Applies To
  • Okta Verify
  • Okta Identity Engine (OIE)
  • Okta Classic Engine
Cause

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.

Solution

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.

Loading
Adding an Account in Okta Verify When Having a Custom Domain