Okta provides the Interaction Code Flow (IDX) grant type as an extension to the OAuth 2.0 and OpenID Connect standard to enable customized user authentication experiences. The Authentication Pipeline that IDX uses is a proprietary application programming interface (API) that lacks direct documentation. Applications must use supported methods to authenticate with IDX, such as Okta-hosted login, embedded widgets, or specific software development kits (SDKs).

• Okta Identity Engine (OIE)
• Interaction Code Flow (IDX)
• okta-idx-java SDK
• okta-idx-android SDK
• okta-idx-dotnet SDK
• okta-idx-swift SDK
• okta-auth-js SDK
• okta-signin-widget

How do applications authenticate with the Interaction Code Flow?

Okta introduces an extension to the OAuth 2.0 and OpenID Connect standard called the Interaction Code Flow (IDX) grant type. This grant type enables the creation of a customized user authentication experience. The Authentication Pipeline that IDX uses is a proprietary API that lacks direct documentation.

Applications must use one of the supported SDKs to authenticate with IDX:

• Okta-hosted login (Redirect authentication)
• Embedded okta-signin-widget
• Embedded okta-auth-js
• Server-side IDX SDKs:
  • okta-idx-java
  • okta-idx-dotnet
• Mobile SDKs:
  • okta-idx-swift
  • okta-idx-android

NOTE: Okta does not provide documentation to use the IDX Authentication Pipeline directly.

Related References

• Embedded Sign-In Widget use cases | Okta Developer
• Embedded Okta Sign-In Widget fundamentals | Okta Developer
• Sign in to SPA with the embedded Okta Sign-In Widget | Okta Developer
• Sign in to SPA with Auth JS | Okta Developer
• Embedded SDK use cases | Okta Developer