Identity Assertion JWT Authorization Grant (ID-JAG)
The Identity Assertion JWT Authorization Grant (ID-JAG) is a signed JWT, issued by an enterprise identity provider through OAuth 2.0 Token Exchange (RFC 8693), that a client presents as a JWT authorization grant (RFC 7523) to a third-party authorization server to get an access token for that server's API without a user consent prompt. It is defined in draft-ietf-oauth-identity-assertion-authz-grant, an active IETF OAuth Working Group draft that is not yet an RFC as of October 2026.
The flow has three steps: the user signs in to the requesting app through the IdP with OpenID Connect or SAML, the app exchanges that ID token (or a refresh token) at the IdP for an ID-JAG naming the target resource, and the app redeems the ID-JAG at the resource's authorization server. The token carries the typ header oauth-id-jag+jwt and its own token type URN, so it cannot be confused with an ID token. What changes for security teams is where the decision sits: the IdP, not each end user, decides which app may reach which API, and the IdP can refuse or log every connection. ID-JAG is the mechanism behind Cross App Access and the Model Context Protocol's Enterprise-Managed Authorization extension.
See also: Cross App Access, identity chaining, token exchange, MCP authorization, agentic identity, Aaron Parecki, agent identity standards map 2026
Related on Start with Identity
- GlossaryTransaction Tokens (Txn-Tokens)
Transaction Tokens (Txn-Tokens) are short-lived, signed JWTs, defined in the IETF draft [draft-ietf-oauth-transaction-tokens](https://datatracker.ietf.org/doc/d
- GlossaryDevice Authorization Grant
An OAuth 2.0 flow (RFC 8628) for input-constrained devices like TVs and CLIs. The user authorizes on a second device using a short code. Device code flow is the
- GlossaryGNAP (Grant Negotiation and Authorization Protocol)
GNAP, the Grant Negotiation and Authorization Protocol ([RFC 9635](https://www.rfc-editor.org/rfc/rfc9635), Proposed Standard, October 2024), is an IETF delegat
- BlogBlack Hat USA 2026 recap: passkeys get broken (twice), and AI agents get an identity perimeter
Our identity takeaways from Black Hat USA 2026: two independent passkey implementation attacks, a wave of AI agent identity and governance launches, an open sou
- BlogIdentiverse 2026 recap: agentic identity grows up, and passkeys get real
Our takeaways from Identiverse 2026 in Las Vegas: AI agent identity moved from theory to roadmap, passkeys turned operational, deepfakes pressured identity veri
- CVEZitadel JWT auth grant ignores key expiration
Zitadel's JWT authorization grant did not check whether the client key had expired. A retired key kept working. Patched by the project.