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. This article explains the behavior of applications that use the v1/sessions/me API after an organization upgrades to the Okta Identity Engine (OIE). After the upgrade, existing embedded sign-in widgets and applications using older Software Development Kits (SDKs) or direct APIs continue to function. However, these applications cannot use new OIE features without modification. Additionally, the API response for v1/sessions/me no longer returns Identity Provider (IdP) information.
- Application Programming Interface (API)
- Software Development Kits (SDKs)
No immediate action is required post-upgrade for applications using the v1/sessions/me API to maintain functionality due to backward compatibility.
NOTE: To adopt new OIE features such as Passwordless authentication or application-specific sign-on policies, applications must be updated to use the latest SDKs that support the Identity Engine Interaction Code flow.
