Testing the Okta Identity Engine Upgrade Rollback Process

Okta administrators cannot test the Okta Identity Engine (OIE) upgrade rollback process because Okta restricts rollbacks to business-impacting use cases. Okta engineering teams extensively test the rollback execution process internally. Administrators upgrading from Okta Classic Engine to OIE often request to test the rollback process in a preview environment before upgrading production. While Okta recommends preparing for and testing the OIE upgrade in a preview environment, the upgrade is a permanent change. In extremely rare edge cases, an Okta environment encounters issues that require Okta engineers to roll back the environment to address the problem before administrators perform the upgrade again.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Upgrade

Can administrators test the Okta Identity Engine upgrade rollback process?

Okta does not provide the ability for administrators to test the OIE upgrade rollback. Okta engineering teams continually and extensively test the rollback execution process. Okta permits rollbacks only for business-impacting use cases to preserve support and engineering resource capacity.

Okta restores all settings to the pre-upgrade state during a rollback.

During the rollback process, Okta restores all settings to the pre-upgrade state. Administrators must manually reapply any configuration changes made after the initial upgrade. Okta provides strict guidelines advising administrators against making substantial changes to the Okta configuration or integrations until there is high confidence that all systems function as expected. A wait time of one to two weeks post-upgrade ensures all use cases receive significant usage and clears any potential rollback requirements.