Okta Identity Engine Upgrade Changes Login ID Values for Username and Password

Upgrading to Okta Identity Engine (OIE) changes the HTML element identifier values for the username and password fields on the sign-in page. Scripts or integrations relying on the Okta Classic Engine values must update the identifiers to match the new OIE values. In Okta Classic Engine, inspecting the username and password elements reveals the values okta-signin-username and okta-signin-password. After upgrading to OIE, Okta changes these element values to input28 for the username and input36 for the password. The following images show the browser's developer tools inspecting the updated values for the username and password fields.

Okta Classic Engine

Okta Identity Engine:

 

 

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Post-upgrade changes

In the DOM structure, id and class values can change across generations and even between major, minor, and patch versions of the Sign In Widget. Okta does not provide information on when these values will change.

How are the login identifier values updated after an Okta Identity Engine upgrade?

Update any custom scripts, automated testing tools, or integrations that reference the Okta Classic Engine login identifiers to use the new OIE values by applying the following replacements.

• Replace okta-signin-username with input28.
• Replace okta-signin-password with input36.

If hooking into the Sign In Widget elements for customization or testing, it would be advised to use the data-se attributes. These are less likely to change, as these are also used for Okta's internal automation testing.

• A JS example for the username:

  document.querySelectorAll('[data-se="o-form-input-identifier"] > input[name="identifier"]')