This article details how Okta Identity Engine (OIE) upgrades might affect Okta Verify and Device Trust functionalities and whether there are any effects on SAML applications. The queries primarily revolve around any possible impacts on authentication flows, existing downstream app federations, and the incorporation of new functionalities like FastPass post-upgrade.
- SAML Applications
- Okta Identity Engine (OIE)
- Okta Verify
- Device Trust
- FastPass
- Authentication Flows
The interest stems from the introduction of the Okta Identity Engine (OIE) upgrade and the uncertainties revolving around the possible changes or adjustments required for SAML applications and other functionalities.
No Impact on SAML Apps: There should be no impact whatsoever. The changes in authentication flow in OIE are primarily on the "front end" – that is, in the authentication to Okta itself. The way Okta asserts identities into SAML apps does not change, ensuring that no modifications are required for existing downstream app federations.
Okta Verify: Existing Okta Verify functionality remains unaffected by the OIE upgrade. Post-upgrade, there is the added ability to enable new functionalities in Okta Verify, specifically FastPass. For more information on FastPass, refer to the FastPass Deployment Guide or the "Password-less" Webinar on the Okta YouTube channel.
Mobile Device Trust: Mobile device trust must be disabled before proceeding with the OIE upgrade. It can then be re-enabled and configured post-upgrade. For more details, refer to the Mobile Device Trust Guide.
Desktop Device Trust: Desktop device trust can remain in place through the upgrade and can be converted to the new Okta Verify managed framework post-upgrade. For additional information, refer to the Migration Guide.
Related References
- The information above was taken from the Ask Me Anything Series on 8/24/23 with the OIE Product Team
