Okta Identity Engine Resources

Steps on how to upgrade and resources readily available to support you.

The Okta Identity Engine upgrade timeline

Follow these four steps to complete your migration from Classic Engine to Identity Engine.

1

Access Upgrade Hub

Log in to Admin Console → Upgrade Hub to see your personalized action items and org-specific upgrade checklist.

2

Review & Prepare

Use the Hub's findings to audit your integrations. Resolve any action items — most orgs have few or none.

3

Test (Recommended)

If you have a Preview or Sandbox org, upgrade it first. Especially important if you've customized authentication, user onboarding, recovery flows, or multiple sign-in policies.

4

Schedule Production

Return to the Upgrade Hub to schedule your production migration. Pick a low-traffic window.

What changes on Okta Identity Engine

The impact varies based on how your applications integrate with Okta.

Minimal Impact

Standards-Based Apps

If your applications use standard SAML or OIDC redirect to the Okta-hosted sign-in page, no code changes are required. Your upgrade is seamless.

  • SAML 2.0 integrations — no changes needed
  • OIDC apps using Okta-hosted sign-in — no changes needed
  • Admin Console experience updates automatically
Review Required

Embedded Flows & SDKs

If you use embedded Sign-In Widget, Okta SDKs, or custom auth APIs, review our migration guide before scheduling your production upgrade.

  • Embedded Sign-In Widget — upgrade to v7+
  • Okta Auth JS SDK — update to v7+ compatible version
  • Custom sign-in pages — validate against new flows