Behavior after a rollback
Your org isn't restored to its previous state after you roll back to Classic Engine. If you made org changes in Identity Engine, some of those changes may persist when you return to Classic Engine. Other features are restored to the default settings.
Changes that persist
-
Users, groups, and applications that you created in Identity Engine persist when you roll back.
-
New users who signed up in Identity Engine persist when you roll back.
-
Recovery and authentication factors that users configured in Identity Engine persist when you roll back.
-
Password and profile changes that users made in Identity Engine persist when you roll back to Classic Engine.
-
If you enrolled Phone as an authenticator in Identity Engine, both SMS and Phone are available for authentication when you roll back to Classic Engine.
-
If you disabled Mobile Device Trust or Self-Service Registration in Classic Engine before your upgrade, these features remain disabled when you roll back. If you enable them again in Classic Engine, the settings are restored to the defaults.
-
Push notifications and TOTP are enabled, even if you didn't have them enabled in Classic Engine before the upgrade.
Changes that don't persist
-
New authentication policies, global session policies, and policy settings created in Identity Engine are restored to Okta default settings after rollback.
-
Changes to password recovery or MFA enrollments made in Identity Engine are restored to Okta default settings after rollback.
-
New Identity Engine functionality like Okta FastPass is deactivated after rollback.
-
The Sign-In Widget is restored to the Classic Engine version after rollback.
-
Links in activation and recovery emails may not work after rollback.
-
Security Questions that were previously configured for both account recovery and MFA are reset to recovery only after rollback.
-
Users sessions are ended. They need to re-authenticate after you roll back.