This article details how an application can make use of the Okta Interaction Code Flow (IDX) in an Okta Identity Engine (OIE) Org. 

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

Okta has introduced an extension to the OAuth 2.0 and OpenID Connect standard called the Interaction Code grant type (IDX). This grant type enables the creation of a more customized user authentication experience.

The Authentication Pipeline used with IDX is a proprietary API that is currently not documented.

Supported methods to authenticate with IDX are:

• Okta hosted login (that is, 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

At this time, there is no 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