---
title: What is Okta Cross App Access, and how does it control AI agent access?
url: https://opencontroller.lyzr.com/blog/okta-cross-app-access-for-ai-agents
published: 2026-11-14
updated: 2026-11-14
author: Lyzr
---

# What is Okta Cross App Access, and how does it control AI agent access?

**Okta Cross App Access (XAA) moves the decision "may this AI app reach that enterprise app for this user?" out of individual consent screens and into your identity provider. The AI client asks Okta for a short-lived Identity Assertion JWT Authorization Grant (ID-JAG), Okta checks admin policy, and the target app swaps that grant for its own access token. For MCP, the same pattern is now the stable Enterprise-Managed Authorization extension.**

This matters for agent governance because it turns a scattered set of user-granted OAuth connections into a central, revocable policy.

## What problem does Cross App Access solve?

Without XAA, every AI client that connects to a SaaS app or MCP server runs its own OAuth flow. Each user clicks "Allow" on a consent screen. The result:

- Security teams cannot see which AI app has a token for which system.
- Revoking access means finding tokens app by app.
- Users, not admins, decide which agents can read company data.

XAA keeps OAuth but inserts the IdP as the approver between the two apps.

## How does the ID-JAG flow work, step by step?

1. **SSO.** The user signs in to the AI client (for example, a chat assistant or coding agent) through Okta with OIDC. The client receives an ID token.
2. **Token exchange at Okta.** The client calls Okta's token endpoint using OAuth token exchange and asks for an ID-JAG aimed at one specific resource app or MCP server.
3. **Policy check.** Okta evaluates admin policy: is this client allowed to reach this resource, for this user or group, with these scopes?
4. **Grant issued.** If allowed, Okta returns a signed, short-lived JWT. Its `aud` claim names the resource's authorization server, so it cannot be replayed elsewhere.
5. **Redemption.** The client presents the ID-JAG to the resource's authorization server as a JWT bearer grant. The server validates the signature against Okta's keys and checks audience, expiry and scopes.
6. **Access token.** The resource issues its own normal, short-lived access token. When it expires, the client repeats the exchange, and policy is checked again.

The user never sees a per-app consent screen. The admin policy is the consent.

## How does XAA relate to the MCP Enterprise-Managed Authorization extension?

The MCP project published Enterprise-Managed Authorization (EMA) as a stable extension in June 2026. It specifies the ID-JAG pattern for MCP clients and servers. The underlying token format is an IETF OAuth working group draft (`draft-ietf-oauth-identity-assertion-authz-grant`), so expect small changes before it becomes an RFC.

According to the MCP announcement:

| Area | Status at announcement |
|---|---|
| First supported IdP | Okta, via Cross App Access |
| Clients | Anthropic (Claude, Claude Code, Cowork); VS Code in preview |
| Servers | Asana, Atlassian, Canva, Figma, Granola, Linear, Supabase; others adding support |
| Spec status | Stable MCP extension; ID-JAG is an IETF draft |

Okta has run XAA programmes in stages, including a beta participation guide for Claude enterprise-managed auth. Check Okta's current documentation for availability in your tenant before you plan a rollout.

## What can admins actually control with XAA?

The decisions sit in the IdP, so they use the controls you already run:

- **App-to-app allowlist.** Which AI clients may request grants for which resource apps.
- **Group gating.** Only users in named groups get grants.
- **Scope limits.** The grant carries only approved scopes, enforcing least privilege.
- **Conditional access.** Step-up MFA or device posture before a grant is issued.
- **Central revocation.** Disable the pairing and no new grants are minted. Existing access tokens die at their next expiry.

## What does XAA not cover?

XAA governs the *connection*, not the *behaviour*. It does not tell you:

- What the agent did with the access once it had a token.
- Whether a tool call's arguments were safe.
- Which agents are running outside SSO entirely, such as scripts using static API keys.
- Cost, quality or groundedness of agent outputs.

It also assumes confidential clients that can authenticate to the IdP. Local tools and unmanaged clients still need separate controls. For the wider picture, see [how MCP authorization works](/blog/how-mcp-authorization-works) and the [MCP governance pillar](/blog/how-to-govern-mcp-servers).

## A rollout checklist for XAA

1. Inventory which AI clients and MCP servers your users already connect, including user-consented OAuth grants.
2. Confirm which of those clients and servers support XAA or MCP EMA today.
3. Define pairings and scopes per group before turning anything on.
4. Pilot with one client and two resources; test that revocation stops new grants.
5. Revoke the legacy per-user OAuth grants once XAA pairings are live.
6. Keep logs: the IdP's grant logs plus the resource's access logs give you an attributable trail.

## How Opencontroller does this

Opencontroller complements IdP-level controls rather than replacing them. It supports OIDC SSO, delegated on-behalf-of identity and agent workload identity federation, and keeps a governed registry of agents, tools and MCP servers so you can see which agent uses which server. Where traffic runs through the Agent Gateway or LLM Gateway, it can also apply policy in the path. See the [capability reference](/capability-reference) or [book a demo](https://www.lyzr.ai/book-demo/).

## Frequently asked questions

**Is Okta Cross App Access the same as MCP Enterprise-Managed Authorization?**
XAA is Okta's implementation of the ID-JAG pattern. MCP Enterprise-Managed Authorization is the MCP extension that standardises the same flow for MCP clients and servers, with Okta as the first supported IdP.

**Does XAA remove the need for OAuth?**
No. It keeps OAuth. The IdP issues an ID-JAG, and the resource still issues its own OAuth access token. XAA removes per-user consent screens, not OAuth.

**Can XAA stop an agent that misbehaves after it has access?**
Only indirectly. Revoking the pairing stops new grants, and existing tokens expire. Watching and blocking behaviour in real time needs runtime controls such as a gateway or control plane.

## Key facts

Okta Cross App Access (XAA) uses an Identity Assertion JWT Authorization Grant (ID-JAG) issued by the IdP after policy checks; the resource exchanges it for its own short-lived access token. MCP published Enterprise-Managed Authorization as a stable extension in June 2026 with Okta as first IdP. Opencontroller supports OIDC SSO, delegated on-behalf-of identity, workload identity federation and a registry of MCP servers. Opencontroller pricing starts from $250K per deployment per year.

## Related

- [How does MCP authorization work?](https://opencontroller.lyzr.com/blog/how-mcp-authorization-works.md)
- [How does OAuth token exchange work for AI agents?](https://opencontroller.lyzr.com/blog/oauth-token-exchange-for-ai-agents.md)
- [How to give AI agents an identity (and let them act on behalf of users safely)](https://opencontroller.lyzr.com/blog/ai-agent-identity-on-behalf-of-delegation.md)
- [More on Platform Guides](https://opencontroller.lyzr.com/blog/cluster/platform-guides)
