Cross App Access
XAA · Cross Application Access · ID-JAG
Okta's OAuth extension that lets an app request access to another app for a user, with user, agent and resource app bound cryptographically. It uses ID-JAG, a JSON Web Token (JWT) authorization grant.
In our briefings
The claim each of the newest briefings on Cross App Access would have you leave with.
October's releases differ on whose identity an agent acts under. Okta and Google tie the call to the user. An MCP server registered in Okta can exchange a user's access token for a downstream token, GA in preview on October 28, so downstream systems log the user. Okta's act claim, GA in production this month, also names the service app that requested an exchange and can chain up to five of them. Google's federated query mode reaches data through MCP connectors with each user's own credentials, in preview since October 2. GitHub moved the other way for shared work: shared Copilot Automations now run as Copilot instead of their creator, as of October 28, while personal automations ran under the creator's identity. A GitHub App can also call Copilot as a workload-owned identity, in public preview since October 27. Prisma AIRS, GA on October 25, logs actions against both the agent and the human.
Okta and Google tie an agent's calls to the user, while GitHub's shared Copilot automations now act as CopilotBI-FIND-2026-2103
Authors from Anthropic, OpenAI, Okta, Defakto Security and Ping Identity propose that an authorization server register an agent platform's Workload Identity Provider once, after which it does not reject an agent just because it has never seen it. The provider signs a JWT naming one agent by an opaque identifier that is never reassigned, and the agent presents it through the existing RFC 7523 JWT-bearer grant. The server checks the grant against the one registration it matches and that registration's keys, grants access under its own policy, and can cap how many new agents a registration brings. A server "MUST NOT require a client registration per Agent". The authors' reason is what happens today: every agent of an installation ends up sharing one credential, "at the cost of any attribution of an individual agent's actions".
Register a platform's identity provider once, not each agent: trust rests on its issuer, with no revocationBI-FIND-2026-0521
WorkOS's checklist limits a delegated agent to the intersection of what the agent is allowed to do and what the user it acts for is "currently allowed to do," and says to check both on every tool call, not once per session. Its example code reads the agent's ceiling from the token and makes a live check for the user, and its test is that revoking a user's access to a project mid-task makes the agent's next call on that project fail. In the post's own example, an agent whose ceiling includes projects:delete still cannot delete a project the user cannot.
WorkOS's agent checklist limits a delegated agent to what it and its user may both do, checked on every callBI-FIND-2026-1997
›Cited in 27 briefings
Every briefing that discusses this term, newest first.
- Okta and Google tie an agent's calls to the user, while GitHub's shared Copilot automations now act as Copilot
Release tracker · · 11 vendors' release notes · Oct 2026
- Register a platform's identity provider once, not each agent: trust rests on its issuer, with no revocation
Draft · · IETF Datatracker · Paul Carleton et al. · Sep 22, 2026
- WorkOS's agent checklist limits a delegated agent to what it and its user may both do, checked on every call
Article · · WorkOS Blog · Maria Paktiti · Sep 30, 2026
- OAuth's draft for token requests that wait on a person now gives the client a link for the user to approve
Draft · · IETF Datatracker · Guilherme de Oliveira Niero et al. · Sep 23, 2026
- Cross-App Access draft warns that one stolen sign-in token could reach every app the identity provider permits
Draft · · IETF Datatracker · Aaron Parecki et al. · May 21, 2026
- A cross-domain transaction-token grant now names AI agents as a use and keeps the call chain at home
Draft · · IETF Datatracker · George Fletcher et al. · Sep 10, 2026
- Agents and MCP servers get broad standing access because it is quick or easy, three voices say, and three vendors now pitch a gateway in front of MCP
Field signals · · 9 voices from the field · Sep 2025 to Oct 2026
- AAuth carries the signals an agent's approval needs, Hardt says; the brain that decides does not exist yet
Podcast · · Collateral Dialogue · Self-Driving Software: What OAuth Can’t Do for AI Agents | Dick Hardt, Hello · Sep 2, 2026
- SaaS apps that only know users end up giving agents human accounts, says Okta's former chief architect
Podcast · · The Identity Jedi Show: Where Identity Meets Strategy · Agents need a mission, not a key. · Oct 21, 2026
- OpenA2A's draft aims to keep secrets from the agent, and says no implementation yet supports its new controls
Draft · · IETF Datatracker · Abdel Fane, OpenA2A · Oct 2, 2026
- Three vendors now route MCP tool calls through an identity check, and only Cloudflare's is generally available
Release tracker · · 11 vendors' release notes · Sep 2026
- Okta says its agent kill switch revokes all tokens; its product screen says tokens outside the gateway survive
Video · · Okta · Sep 24, 2026
- Okta's Oktane keynote: two agent products generally available now, support for other identity providers in 2027
Video · · Okta · Sep 23, 2026
- Okta's September videos: six customer stories with few measured results, and keynote recaps that drop the ship dates
Channel digest · · Okta (Oktane) · Sep 2026
- NIST's agent identity work starts from OAuth, SPIFFE and SCIM and defers agents from outside the enterprise
Article · · NIST National Cybersecurity Center of Excellence · Harold Booth et al. · Feb 5, 2026
- MCP's enterprise login extension says IdP revocation is immediate. Its own spec does not back that up
Article · · Model Context Protocol (modelcontextprotocol.io) · MCP project et al. · Jun 18, 2026
- PayPal moved MCP tool permission checks into the server, and prompt-injected agents stopped getting through
Paper · · arXiv · Huan Li et al. · Sep 18, 2026
- OAuth handles an agent in one company, working while you watch. The OpenID paper says that is where it stops.
Article · · OpenID Foundation · Tobin South et al. · Oct 2025
- Okta's answer to agent sprawl: put the identity provider between every agent and every app
Podcast · · Cloud Security Podcast · Who Governs Your AI Agents? Identity, Offboarding & Open Standards · Jul 2, 2026
- Batch delegation assigns each permission to an agent, then filters at token exchange
Draft · · IETF Datatracker · Yuan Ni et al. · Jul 3, 2026
- Three vendors put MCP controls in three different places in May, and only Auth0's was GA
Release tracker · · 10 vendors' release notes · May 2026
- Microsoft and Google made AI agent identity generally available in April; Okta's notes put its GA in May
Release tracker · · 8 vendors' release notes · Apr 2026
- A cross-domain agent trust draft requires the call chain, then leaves its format to a version that never came
Draft · · IETF Datatracker · Daniel King et al. · Mar 15, 2026
- Auth0's case for Token Vault: take the user ID out of the token call and let the session prove whose token it is
Article · · Auth0 Blog · Abhishek Hingnikar, Okta · Nov 4, 2025
- On its authors' tasks, an LLM check of agent scopes works at one tool and refuses most valid three-tool requests
Paper · · arXiv · Majed El Helou et al. · Oct 30, 2025
- OpenID's enterprise login draft adds tenant and session-expiry claims, and its security section is still blank
Article · · OpenID Foundation · Dick Hardt et al. · Sep 25, 2025
- The July 2025 Cross App Access draft lets the IdP decide app-to-app access and treats agents as plain clients
Draft · · IETF Datatracker · Aaron Parecki et al. · Jul 2, 2025
Related terms
What appears alongside Cross App Access in the same briefings.
OktaModel Context ProtocolAnthropicOkta for AI AgentsOkta Agent GatewayIdentity Assertion Authorization GrantAuth0 Token VaultAAuth (Hardt)