<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
Testing the OIE Upgrade Rollback
Okta Identity Engine
Additional Resources
Overview

Okta urges all Classic Org Administrators to upgrade to the Okta Identity Engine (OIE). The upgrade from Classic to Okta Identity Engine (OIE) brings several enhancements and is a permanent change. Orgs that are updated cannot revert to Classic.

 

It is strongly recommended to prepare for and test the OIE Upgrade in a company's Preview Org before performing the upgrade in the company's Production Org. In extremely rare edge cases, an Okta Org may encounter issues that require Okta Engineers to roll back the Org to address the problem before performing the upgrade again.

 

This article addresses whether Okta Org Administrators can test the OIE upgrade rollback process.

 

Applies To
  • Okta Identity Engine (OIE)
  • Upgrade
Solution

Okta cannot provide the ability for customers to test the OIE upgrade rollback. Okta Engineering teams continually and extensively test the rollback execution process. Rollbacks are only permitted for business-impacting use cases to preserve the support and engineering resource capacity.

During the rollback process, all settings are restored to their pre-upgrade state, assuming no configuration changes were made outside of the upgrade process. Any changes must be reverted to the state after the upgrade. 

 

For this reason, Okta provides strict guidelines for not making any substantial changes to the Okta configuration or to its integrations until there is high confidence that all systems are working as expected. Typically, a wait time of one to two weeks post-upgrade is sufficient to ensure all use cases have had significant usage and any potential rollback is cleared.

Recommended content

Loading
Testing the OIE Upgrade Rollback