The following reconfiguration has been identified as part of the preparation needed to perform the upgrade to Okta Identity Engine (OIE).

NOTE: Additional Okta features may require reconfiguration or be disabled to complete the upgrade. This article addresses an error that blocks an upgrade to the Okta Identity Engine (OIE). When attempting the upgrade, the eligibility status shows as Eligible - Okta Assistance Required, and the following error message is displayed:

Additional Consent Required - ENG_OIE_UPGRADE_BLOCKER - Your org has been blocked from being upgraded due to a potential impacting configuration; please contact Support to identify the path to resolution. Provide Org id: <orgId>

• Okta Identity Engine Upgrade

• Sign-in Widget

• Self-Service Registration

The upgrade is blocked because a configuration exists that will function differently or become unsupported after upgrading to OIE. This block prevents potential impacts on user experience or functionality. The two primary configurations that cause this block are:

• An embedded Sign-in Widget with a Self-Service Registration policy enabled.

• Use of the Registration API outside the Sign-in Widget Software Development Kit (SDK).

NOTE: To determine the specific root cause for the block, contact the Account Team or Okta Support with the organization ID or Tenant Name from the error message.

Embedded Sign-in Widget with Self-Service Registration policy enabled [EmbeddedSSR-SIW]

1. Review the current deployment of the Okta Sign-in Widget to verify if the registration feature is enabled.

2. Consult the Embedded Sign-In Widget guide for necessary reconfiguration steps.

3. After identifying any required post-upgrade modifications, contact Okta Support with the Org ID to request the removal of the upgrade block.

NOTE: For lower environments, this block can be removed to assist with production upgrade planning. A known impact in embedded Self-Service Registration, along with validated consent, is not a valid reason for a post-upgrade rollback.

Usage of the Registration API outside the Sign-in Widget SDK

Change to a supported Self-Registration method using one of the following options:

• Method 1 (Preferred): Use the embedded Sign-in Widget, which is the intended use for the API. Consult the Embedded Sign-In Widget guide for implementation details.

• Method 2: Switch to the create user core management API. Refer to the developer documentation for this API.

NOTE: The API endpoint /api/v1/registration/{{SelfRegFormPolicyId}}/register is not supported outside of the Sign-in Widget and will be disabled during the upgrade process.

After completing any necessary pre-upgrade modifications, contact Okta Support with the Org ID to request the removal of the upgrade block.

NOTE: For lower environments, this block can be removed to assist with production upgrade planning. A known impact in embedded Self-Service Registration, along with validated consent, is not a valid reason for a post-upgrade rollback.

Related References

• Embedded Sign-In Widget
• Create user core management API