<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

Okta Preview Tenant Is Inaccessible With a "Page Not Found" Error

Okta Classic Engine
Okta Identity Engine
Okta Verify

Overview

Enabling the Flexible Okta Verify authenticator configuration feature while Okta FastPass remains inactive causes the Okta Preview tenant to become inaccessible. This issue occurs because the database migration creates an inactive authenticator, causing authorize-flow lookups to fail. Resolving this requires activating the authenticator or disabling the feature flag. When users access the tenant, Okta displays the following error:

 

404 - Page Not Found Affected URL: https://<example>.oktapreview.com

 

Applies To

  • Okta Identity Engine (OIE)
  • Okta Classic Engine
  • Okta FastPass
  • Flexible Okta Verify Authenticator Configuration

Cause

Enabling the Flexible Okta Verify authenticator configuration feature triggers a database migration that creates the new okta_verify_fastpass authenticator. If administrators do not actively enable Okta FastPass (Signed Nonce) on the organization before toggling the flag, Okta creates the authenticator with an INACTIVE status. Once administrators enable the flag, all authorize-flow lookups switch to okta_verify_fastpass. Because the authenticator is inactive, Okta throws a resource not found error, which surfaces as a 404 error.

 

Before administrators enable the flag, Okta FastPass lookups use the bundled okta_verify authenticator. After administrators enable the flag, lookups switch to the new okta_verify_fastpass key. If the organization never actively enabled Okta FastPass or if administrators disabled it manually, the migration sets okta_verify_fastpass to INACTIVE. The active-only lookup then fails, generating an AUTHENTICATOR_RNF warning and a 404 error.

Solution

What resolves the Okta Preview tenant 404 error?

Activate the Okta FastPass authenticator or disable the feature flag to resolve the 404 error.

  • Activate the okta_verify_fastpass authenticator on the organization using the Okta Admin Console or the Okta API.
  • Disable the Flexible Okta Verify authenticator configuration feature flag until administrators properly configure Okta FastPass in the organization.
Loading
Okta Preview Tenant Is Inaccessible With a "Page Not Found" Error | Okta Support