Behavior of the v1/sessions/me API After an Okta Identity Engine Upgrade
Last Updated:
Overview
The following reconfiguration has been identified as part of the preparation needed to perform the upgrade to Okta Identity Engine (OIE). Note that additional Okta features may require reconfiguration or be disabled in order to complete the upgrade. After an upgrade, existing embedded sign-in widgets and applications using older SDKs or direct APIs continue to function. However, these applications cannot use new OIE features without modification, and the API response for v1/sessions/me no longer returns Identity Provider (IdP) information.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Application Programming Interface (API)
- Software Development Kits (SDKs)
Solution
What is the expected behavior of the v1/sessions/me API after an Okta Identity Engine upgrade?
Applications using the v1/sessions/me API require no immediate action post-upgrade to maintain functionality due to backward compatibility.
NOTE: Adopting new OIE features, such as Passwordless authentication or application-specific sign-on policies, requires updating applications to use the latest SDKs that support the Identity Engine Interaction Code flow.
