Applies To
- CUSTOMER_HOSTED_SIGN_IN_WIDGET
- Upgrade Eligibility: Customer Consent Required
How does this impact the upgrade to OIE?
Post upgrade,some of the capabilities of the Sign-in widget would be deprecated. Please be sure to review the widget code thoroughly to ensure a smooth transition.
Experience Impact
The Okta embedded Sign-In Widget will continue to operate in "classic mode" when linked to an org that has been upgraded to Identity Engine, with the exception of the Deprecated Features & JavaScript methods found in the link below. As with the hosted Sign-In, all general Identity Engine feature changes (i.e. Password-less Sign-in Policies) will impact embedded instances of the SIW.
Due to the extensibility capabilities with embedding the Okta SIW, we encourage you to review the developer-focused upgrade guidance below:
NOTE: If Self-service Registration is configured this will no longer function until the interactive code flow if configured within the sign-in widget configuration. This is not an automatic detection, it is a manual discovery as part of the "Deprecated Features and JavaScript Methods" link above.
Post-Upgrade Enhanced Experience (Adopt OIE Functionality)
Please see the guide below to assist in upgrading the Okta SIW to use features/capabilities available only with OIE (i.e. Password-less Sign-in Policies and Profile Enrollment). Note: all customer-hosted sign-in widgets must be updated to the latest version and use the "interaction code" grant type to unlock these abilities.
Detecting the origin of Sign-in Widget
debugContext.debugData.requestUri sw "/api/v1/authn" and debugContext.debugData.oktaUserAgentExtended co "signin-widget" and debugContext.debugData.origin pr
