This article provides details about the Interaction Code grant type, specifically whether it is available for Okta Classic Engine or not. Furthermore, the article will describe how the Interaction Code grant type operates in Okta Identity Engine (OIE), including the remediation steps and the differences in SDKs between the two engines.
- Okta administrators
- Developers using Okta Classic Engine
- Okta Identity Engine
- Integrating OAuth 2.0 and OpenID Connect standard with Okta
A need to clarify whether the Interaction Code grant type is accessible in Okta Classic Engine or solely in Okta Identity Engine.
It is important to clarify that the Interaction Code grant type is not available for Okta Classic Engine. Okta's event types list interaction code events exclusively for OIE. These events include 'app.oauth2.as.interact.interaction_code' and 'app.oauth2.interact.interaction_code' which fire when an interaction code is generated by OIE.
The Interaction Code grant type is a new feature introduced to Okta Identity Engine. This grant type, an extension to the OAuth 2.0 and OpenID Connect standard, allows for a more personalized user authentication experience. It allows native, SPA, and web apps to manage user interactions with the authorization server directly.
Interaction Code flow consists of several interactions between the user and the authorization server, facilitated by the client. Each interaction or remediation step corresponds to a piece of user data required by the authorization server. The number and nature of these steps are configurable in the policies.
Okta Identity Engine SDKs support the Interaction Code flow, which is beneficial for App Level MFA. However, the Okta Classic Engine has limited SDK support.
