The following reconfiguration has been identified as part of the preparation for the upgrade to Okta Identity Engine (OIE). Note that additional Okta features may require reconfiguration or be disabled in order to complete the upgrade. This article provides the necessary steps to reconfigure the Okta Hosted Sign-In Widget in preparation for an upgrade to the Okta Identity Engine (OIE). An outdated version of the widget on an Okta Hosted Login Page that uses a custom URL domain can prevent a successful upgrade. This issue does not affect Embedded Sign-In Widget deployments.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Sign-In Widget Version less than 5.11
• Custom URL Domain

Sign-In Widget versions lower than 5.11 cannot utilize the login flows for features introduced in the Okta Identity Engine (OIE).

An inability to upgrade the Okta-hosted widget to the required version prevents the OIE upgrade process from continuing. 

The Okta-hosted Sign-In Widget must be upgraded to the latest release, and any deprecated JavaScript methods must be removed before the upgrade.

The widget upgrade process for a redirect sign-in flow depends on whether a custom URL domain is configured:

• If a custom URL Domain is not configured and there are no customizations beyond simple branding styles, the widget automatically upgrades to the latest version when it loads from the content delivery network (CDN).
• If a custom URL domain is configured with other customizations, an administrator must update the widget version in the Admin Console.

Update the Widget

1. Navigate to Customizations > Brands in the Okta Admin Console.
2. Select the brand that uses the custom domain.
3. Select the Pages tab.
4. Click Configure under the Sign-in Page section.
5. Select the Settings tab.
6. In the Okta Sign-In Widget Version section, click Edit and select the latest version available (for example, ^7).
7. Click Save at the bottom of the page.
8. Test the application's supported authentication, sign-up, and recovery flows to ensure they function correctly.
9. Verify that any custom Cascading Style Sheets (CSS) and localization changes are reflected in the new version.

NOTE: Pinning the instructions to a specific version of the Sign-In Widget is not recommended, as this prevents access to the latest capabilities and bug fixes available at the time of the upgrade.

Resolve Invalid Version Reporting with Multi-Brand Customizations

A known issue can cause the widget version to be detected incorrectly when the multi-brand customization feature is active and the original default brand was not updated. To resolve this, perform the following steps:

1. Disable the multi-brand customization feature in Feature Manager.
2. Navigate to Branding.
3. Edit the Sign-in Page.
4. Enable the Code Editor.
5. Click Save Draft without making changes.
6. Navigate to Settings.
7. Update the widget to the latest version.
8. Click Save Draft without making other changes.
9. Click Save and Publish.
10. Re-enable the multi-brand customization feature.

Related References

• Upgrade process for a redirect sign-in flow 
• Deprecated JavaScript methods in the widget