Telemetry detected that modifications have been made to the Okta Hosted Sign-In page (CUSTOM_SIGN_IN_PAGE). Custom JavaScript and/or CSS has been applied to the hosted widget. Consent is required before the upgrade can proceed. Review the widget customizations to confirm compatibility with Okta Identity Engine before providing consent.

Applies To

• CUSTOM_SIGN_IN_PAGE
• Upgrade Eligibility: Eligible — Consent Required

After reviewing and remediating customizations, eligibility will advance to Eligible — Ready to Upgrade once consent is provided.

Experience Impact

The Okta Hosted Sign-In page has been modified with custom JavaScript and/or CSS. After upgrading to Identity Engine, the widget runs in OIE mode by default. Classic Engine widget APIs and deprecated methods will no longer function as expected.

Common sources of breakage to investigate:

• Deprecated JavaScript methods — Methods valid in Classic Engine may not be available or may behave differently in OIE. See the developer guide linked in the References section.
• Extended Flows JavaScript — Code that uses OktaUtil.getRequestContext to switch behavior based on application context should be reviewed for OIE compatibility.
• CSS overrides — Style overrides tied to Classic widget DOM structure may need adjustment after the upgrade.
• Self-Service Registration (SSR) — If SSR was configured via the Classic widget, it must be reconfigured using Profile Enrollment Policies in OIE.

Before the Upgrade

Review the widget customizations, remove deprecated JavaScript methods, and validate the updated sign-in page in an OIE-enabled preview environment before upgrading production.

1. Identify the current Sign-In Widget version deployed on the hosted page.

2. Review all custom JavaScript for use of deprecated methods and OktaUtil.getRequestContext usage.

3. Review CSS overrides for dependency on Classic widget DOM structure.

4. Check whether Self-Service Registration is configured on the hosted page.

5. Update the Sign-In Widget to the latest version and remove all deprecated JavaScript methods.

6. Validate the updated customizations in an OIE-enabled preview environment before upgrading production.

After the Upgrade

Parity: No parity changes are required — the hosted widget advances to OIE Enhanced Experiences by default.

Enhanced Experience (OIE Functionality):

• Discovery Dependent: Review and update Email Templates (Activation and Recovery)
• Discovery Dependent: Migrate Self-Service Registration to Profile Enrollment Policies
• Discovery Dependent: Update Sign-In Widget JavaScript/CSS for OIE widget structure
• Enhance with Sign-in Policies (Global Session and Authentication policies)
• Enhance with Profile Enrollment Policies

Related References

• Upgrade to Okta Identity Engine
• Sign-in Widget upgrade guide
• Upgrade the Okta Sign-In Widget
• OIE upgrade overview
• Deprecated JavaScript methods
• Stretch Your Imagination and Build a Delightful Sign-In Experience
• Unlock the Secrets of a Custom Sign-In Page with Tailwind and JavaScript

AI Code Review Prompt

To help prime an LLM that may be assisting with a code assessment, copy the prompt below and paste it into any AI assistant. Replace [PASTE SOURCE CODE HERE] with the full HTML/JS/CSS of the custom sign-in page. AI findings are a starting point — verify all results through end-to-end testing before making production changes.

You are an Okta Sign-In Widget specialist. Review this custom Okta-hosted sign-in page for OIE upgrade compatibility.

[PASTE SOURCE CODE HERE]

---

WHAT TO CHECK:

Deprecated feature flags (+1 pt each if present):
features.idpDiscovery, features.rememberMe, features.autoPush, features.smsRecovery,
features.callRecovery, features.webauthn, features.selfServiceUnlock,
features.multiOptionalFactorEnroll, features.registration,
features.showPasswordToggleOnSignInPage, features.scrollOnError,
features.skipIdpFactorVerificationBtn

High impact (+3 pts each): registration: {  |  .setCookieAndRedirect(  |  processCreds:
Medium impact (+2 pts each): .preSubmit( or .postSubmit(  |  parseSchema:
Low impact (+1 pt): idps: [  (still works in OIE, no change required)

CSS rules targeting #okta-sign-in or .auth-container: 1–10 = +1 | 11–30 = +2 | 30+ = +3
i18n overrides (config.i18n or englishLanguage[): +1
Event hooks (oktaSignIn.on(): +1

EFFORT TIER:
0 = DEFAULT (no findings)  |  1–4 = LOW  |  5–9 = MEDIUM  |  10–14 = HIGH  |  15+ = CRITICAL

---

OUTPUT:
For each finding: matched line with ±1 line context, OIE impact explanation, and remediation action.
Close with a scored summary table, effort tier, and priority-ordered action list.
Cite links from the reference list below where applicable.

---

REFERENCE LINKS:
Deprecated feature flags / widget upgrade: https://developer.okta.com/docs/guides/oie-upgrade-sign-in-widget/main/
Deprecated JavaScript methods: https://developer.okta.com/docs/guides/oie-upgrade-sign-in-widget-deprecated-methods/main/
setCookieAndRedirect: https://developer.okta.com/docs/guides/oie-upgrade-sessions-api/main/
Registration block: https://support.okta.com/help/s/article/OIE-Incompatible-FF-SELFSERVICEREGISTRATION
CSS / custom sign-in page: https://help.okta.com/oie/en-us/content/topics/identity-engine-upgrade/self-service/custom-sign-in-page.htm
OIE upgrade overview: https://developer.okta.com/docs/guides/oie-upgrade-overview/main/
General upgrade hub: https://support.okta.com/help/s/product-hub/oie/upgrading-to-okta-identity-engine