Okta Does Not Support XAA When an Okta Authorization Server Protects the Application
Last Updated:
Okta Identity Engine
Okta For AI Agents
Overview
Okta does not support XAA when an Okta Org Authorization Server (AS) or a Custom Auth Server protects the XAA Application. This limitation occurs because the Managed Connection Issuer requires a non-Okta Issuer. Configure the Managed Connection Issuer to use a non-Okta Issuer to successfully establish the connection.
Applies To
- Okta Identity Engine (OIE)
- XAA
- Authorization Servers
Cause
The configuration uses an Okta Issuer, such as an Okta Org Authorization Server or Custom Authorization Server, for the Managed Connection Issuer. Okta currently does not support this configuration.
Solution
How is the XAA application connection configured?
Configure the Managed Connection Issuer to use a non-Okta Issuer to successfully establish the connection.
- Ensure that the Managed Connection Issuer is not an Okta Issuer.
- Remove any Okta Org AS or Custom Auth Server configurations from the Managed Connection Issuer.
