Okta Opens AI Agent Governance to Third-Party Identity Providers
Okta's generally available third-party IdP support for AI Agents lets Ping, Descope and Oracle customers govern agent access without replacing their identity stack, using short-lived scoped tokens.
By Daniel Okafor
4 min read

What's News
- Third-party IdP support for Okta for AI Agents and Agent SSO is generally available now, working with Ping, Descope and Oracle via the XAA standard
- Okta replaces static API keys and shared service accounts with short-lived, scoped tokens for MCP server connections
- A kill-switch integration with ServiceNow is in limited release; Blueprint Alliance partners include AWS, CrowdStrike, Databricks and Google Cloud
- OneMain Financial is cited as a customer; production deployment numbers are not disclosed
By Daniel Okafor
Okta has made third-party identity provider support for Okta for AI Agents and Agent SSO generally available, letting enterprises govern AI agent access across different identity systems without replacing their existing stack. The feature works with XAA-enabled IdPs including Ping, Descope, and Oracle. It builds on Cross App Access (XAA), an open standard Okta spearheaded.
The timing targets a specific pain point. Companies that grow through acquisitions inherit multiple identity providers, and merging them takes years. AI agents now multiply that problem because every agent needs credentials. Okta's pitch: govern agents now, consolidate identity later — or never.
What does the new capability actually do?
Customers 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 is required, the company said.
When an employee calls an agent, the agent presents a token issued by its home IdP. Okta verifies the token and issues a scoped, short-lived token for only the resource the agent needs. The employee signs in once, with no per-agent consent prompts.
Harish Peri, SVP and GM of AI at Okta, framed the problem bluntly. "AI isn't going to consolidate on one platform, and neither are the identity providers companies inherit through acquisitions and partnerships," Peri said. "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."
How the token flow works under the hood
Developer documentation describes the mechanism. Okta acts as the resource authorization server while the external IdP issues the Identity Assertion JWT Authorization Grant (ID-JAG). The 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.
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. 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.
What do customers say?
OneMain Financial is cited as a customer in Okta's press release. 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."
Where does XAA extend next?
A companion blog post detailed two additional areas of coverage:
- 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. This replaces static API keys and shared service accounts.
- Third-party MCP servers. XAA now extends to external XAA-supported MCP servers. IT can enforce central policies over external connections instead of relying on scattered user consent screens.
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?" The Blueprint Alliance, which Okta co-founded, includes AWS, CrowdStrike, Databricks, Google Cloud, and ServiceNow. Okta integrates with these partners for agent discovery and registration, and a kill-switch integration with ServiceNow is in limited release.
How solid are the claims?
Okta claims the capability reduces onboarding from years to a single quarter, eliminates consent fatigue, and provides a single audit trail and kill switch across any XAA-participating authorization server. The press release carries the standard caveat: items "not currently generally available... may not be delivered or obtained on time or at all." The third-party IdP support itself is generally available today for Okta for AI Agents and Agent SSO customers.
The sources provide no independent verification of customer deployments, performance, or comparative advantage over alternative approaches. XAA adoption beyond the vendors named — Ping, Descope, Oracle, Linear, Notion, Slack — is not detailed. The developer documentation confirms the technical flow but does not attest to production readiness at scale.
Several questions remain open: how many enterprises run this in production versus pilot, whether the "this quarter" onboarding claim holds in complex multi-IdP environments, how far XAA adoption reaches among SaaS vendors, and whether pricing changes for existing Okta for AI Agents customers.
The announcement is a concrete step toward multi-IdP agent governance built on an open standard. Whether it becomes the default layer for agent identity across heterogeneous environments depends on XAA adoption by other IdP and SaaS vendors — something the sources do not measure.
Source: epyhia.com
More from Daniel Okafor
Show full bio
Correspondent covering money, funding and market shifts around entrepreneurship, startups and venture funding at Business Bearings.
2,427 articles