Separating AI hype from reality.

Okta Launches Out-of-the-Box Identity Governance for AI Agents Across Multiple IdPs

November 20, 2026 · Okta · Security

Okta announced general availability of third-party identity provider support for Okta for AI Agents and Agent SSO, letting enterprises govern AI agent access across different identity systems without replacing their existing identity stack [1]. The feature builds on Cross App Access (XAA), an open standard Okta spearheaded, and works with XAA-enabled IdPs including Ping, Descope, and Oracle [1].

What was announced

Okta says customers can now connect an XAA-enabled third-party IdP to Okta once, sync users into Okta, and register that IdP's agents as clients in Okta for AI Agents—no custom connector required [1]. When an employee calls an agent, the agent presents a token issued by its home IdP; Okta verifies it and issues a scoped, short-lived token for only the resource the agent needs [1]. The employee signs in once, with no per-agent consent prompts [1].

The company frames this as solving the "multi-year identity consolidation" problem that follows acquisitions and partnerships. "AI isn't going to consolidate on one platform, and neither are the identity providers companies inherit through acquisitions and partnerships," said Harish Peri, SVP and GM of AI at Okta [1]. "Agent security has to work across organizations' entire environment, today. With third-party IdP support, companies can bring a new team onto shared agents this quarter, not after a multi-year identity consolidation" [1].

How the external IdP flow works

Technical documentation shows Okta acts as the resource authorization server while the external IdP issues the Identity Assertion JWT Authorization Grant (ID-JAG) [6]. The client (an AI agent) obtains an ID-JAG from the external IdP and presents it to Okta's custom authorization server /token endpoint as a jwt-bearer grant [6]. Okta validates the ID-JAG signature against the IdP's JWKS endpoint, matches the user via a linked identity, and issues a short-lived access token [6]. The external IdP must be configured with "Cross App Access only" or "SSO and Cross App Access" usage; users must exist in Okta and be linked to the IdP [6].

Customer perspective

Tunde Oni-Daniel, Deputy CTO at OneMain Financial, said: "Every company already has an identity stack for humans, and most have more than one. Agent security shouldn't require them to rip it out or wait for one vendor to catch up... Okta has always been that independent layer" [1]. OneMain Financial is cited as a customer; the quote appears in Okta's press release [1].

Broader context: XAA, MCP, and the Blueprint Alliance

The announcement extends XAA governance to two additional areas Okta detailed in a companion blog post [2]:

  • Downstream internal MCP servers: Okta for AI Agents now issues short-lived, scoped tokens for each connection between an internal MCP server and downstream enterprise systems, replacing static API keys and shared service accounts [2].
  • Third-party MCP servers: XAA now extends to external XAA-supported MCP servers, letting IT enforce central policies over external connections instead of relying on scattered user consent screens [2].

Okta positions these capabilities as answering two of the Blueprint Alliance's four architectural questions: "What can my agents do?" and "What are they doing?" [2]. The Blueprint Alliance, which Okta co-founded, includes AWS, CrowdStrike, Databricks, Google Cloud, and ServiceNow [3]. Okta integrates with these partners for agent discovery and registration; a kill-switch integration with ServiceNow is in limited release [3].

Claims versus evidence

Okta claims the capability reduces onboarding from years to "this quarter, not after a multi-year identity consolidation," eliminates consent fatigue, provides a single audit trail and kill switch, and works vendor-neutrally across any XAA-participating authorization server [1][2]. The press release includes a forward-looking disclaimer that items "not currently generally available... may not be delivered or obtained on time or at all" [1]. The third-party IdP support itself is stated as generally available today for Okta for AI Agents and Agent SSO customers [1].

Independent verification of customer deployments, performance, or comparative advantage over alternative approaches is not provided in the sources. The XAA standard's adoption beyond the listed vendors (Ping, Descope, Oracle, Linear, Notion, Slack) is not detailed [1][2]. The developer documentation [6] confirms the technical flow but does not attest to production readiness at scale.

What remains unclear

  • How many enterprises have deployed this in production versus pilot.
  • Whether the "this quarter, not after a multi-year identity consolidation" onboarding claim holds for complex multi-IdP environments.
  • The extent of XAA adoption among SaaS vendors beyond those named.
  • Pricing or licensing changes, if any, for existing Okta for AI Agents customers.

Okta's announcement represents a concrete step toward multi-IdP agent governance using an open standard. Whether it becomes the de facto layer for agent identity across heterogeneous environments will depend on XAA adoption by other IdP and SaaS vendors—something the sources do not measure.

Sources

  1. Okta for AI Agents now works out-of-the-box with multiple third-party identity ... (okta.com)
  2. How to Secure Every Hop in an AI Agent's MCP Workflow (okta.com)
  3. Securing AI Starts with Identity: The Blueprint Alliance Framework (okta.com)
  4. How to secure AI agents in a shifting regulatory landscape (okta.com)
  5. 5 Identity Rules to Secure AI Agents in Manufacturing (okta.com)
  6. Configure XAA with an external IdP | Okta Developer (developer.okta.com)