Okta for AI Agents

Verification notes: GA confirmed via Okta's own announcement. A separate 'Core' tier reached GA for regulated environments (FedRAMP, HIPAA), registering agents as first-class identities with scoped, short-lived tokens replacing hardcoded credentials. Correction this pass: the mcp flag moves from false to true. Okta's own product page explicitly documents MCP governance as a core capability — 'register your agents and MCP servers... in a centralized directory' and 'end-to-end MCP coverage to secure the entire AI agent lifecycle.' A2A stays unconfirmed: Okta states it is 'actively working with the MCP and A2A communities' and offers Cross App Access (XAA), a complementary OAuth extension, but XAA is not A2A itself and no Okta page documents native A2A protocol implementation. Material update this pass: Okta made 'Agent SSO' generally available August 24, 2026, per Okta's own newsroom press release, bundling Cross App Access into core Okta SSO at no extra cost and giving AI agents first-class identity status in Universal Directory with short-lived signed ID-JAG tokens. The same release explicitly states XAA is now formally incorporated as the official 'Enterprise-Managed Authorization' extension for MCP — not for A2A — which reinforces rather than changes the existing a2a=false call. cryptoSigned=true and enterpriseManaged=true are both reconfirmed by this release. See also the newly added CrowdStrike Agentic Identity Provider listing for a large incumbent's comparable but separately-built approach to agent identity. For a distinct vendor with a comparable OAuth-delegation and runtime-gateway approach, see the newly added Ping Identity Identity for AI listing.