Identity Engine upgrade FAQ

Okta Identity Engine is a new way to customize your Okta experience and implement flexible identity use cases. This means shifting from predefined behaviors to a platform that offers customizable building blocks for dynamic, app-based configurations.

Identity Engine is a platform as a service and is available without an extra cost. Most existing features and functionality that you purchased initially are available after your upgrade.

Contact your Okta Customer Success representative or Okta account team about upgrade eligibility and to receive further instructions on how to upgrade.

Okta manages the upgrade to Identity Engine. If applicable, your preview environment is upgraded first to test new functionality. Some changes may need to be made to existing features. This involves disabling unsupported features from Classic Engine.

You'll receive instructions on how to test your org after the upgrade.

Work with your Okta representatives and refer to our product documentation to answer any questions you have about the upgrade process.

All legacy APIs continue to work on Classic Engine but there are two new API sets:

• Policy APIs
• Factor Profiles APIs

See Okta Developer documentation for more information about Identity Engine APIs.

Most Classic Engine features are supported in Identity Engine. This information is communicated to you in advance of an upgrade.

Some orgs are not ready for an immediate upgrade. To find out if your org is eligible, check with your Okta representative.

See Okta Device Trust solutions on a Classic Engine org.

You may submit a request to your Okta account team if you need to revert to Classic Engine.

For more information, see Roll back to Classic Engine.

Yes, app integrations for both SAML 1.1 and 2.0 are supported.