Managing Customizations During an Okta Identity Engine Upgrade

Upgrading to Okta Identity Engine (OIE) requires reviewing and updating existing customizations to ensure continued functionality and access to new features. Custom JavaScript in the Okta Hosted Sign-In Widget may fail if deprecated methods are used, while embedded widgets, SDKs, and APIs require updates to utilize the new authentication pipeline. Review and remediate deprecated methods, upgrade embedded components, and transition to OIE-compatible SDKs or APIs.

How are Okta Hosted Sign-In Widget customizations managed?

If the Okta Hosted Sign-In Widget contains custom JavaScript, the customized JavaScript may fail after upgrading to OIE. Identify deprecated methods, remediate the code, and test the application to ensure the widget functions correctly.

• Check for the use of any deprecated JavaScript methods in the Okta Hosted Sign-In Widget.
• Remediate all deprecated JavaScript methods.
• Test the application and ensure the widget functions correctly.
• Review the Deployment Model for Customized Okta Hosted Sign-In Widget for more details.

The embedded Okta Sign-In Widget requires an upgrade to utilize new features.

Applications hosting the Okta Sign-In Widget, using Okta SDKs for authentication, or directly calling the Okta Authentication API maintain the same user experience after the upgrade. However, these applications continue using the Classic Authentication Pipeline. Upgrade the widget version, test the application, and update the styling and internationalization properties.

• Upgrade the Okta Sign-In Widget to the latest version.
• Test the application to ensure the widget functions correctly.
• Make any necessary updates to the Sign-In Widget styling and i18n properties.
• Review the Deployment Model for Embedded Okta Sign-In Widget for more details.

What updates are required for Okta SDK integrations?

The Okta SDKs offer tighter alignment with the capabilities introduced in OIE. Failing to shift to an Okta-hosted experience or update the Classic SDK prevents the use of new functionality. Add the appropriate OIE SDK to the application code or update to the latest version.

• Add the appropriate OIE SDK to the application code or update to the latest version of the OIE SDK. See Add the latest Auth SDKs to your applications for detailed steps by language.
• Review the Deployment Model for Embedded Okta SDK for more details.

Authentication APIs must be updated to support new sign-in capabilities.

The public Authentication APIs have evolved. Remaining on the Classic /authn API instead of moving to an Okta-hosted experience or an OIE SDK prevents the use of new sign-in capabilities introduced with OIE. Transition to the latest release of the Okta Hosted Sign-In Widget, host the widget within the application, or implement an Okta SDK.

• Transition to the latest release of the Okta Hosted Sign-In Widget and utilize redirects.
• Alternatively, host the Okta Sign-In Widget within the application or use an Okta SDK.
• Review the Deployment Model for Embedded Okta Authentication API for more details.