# What is JWT Bearer Grant?

> An OAuth extension that lets a client trade a signed JSON Web Token, issued by a party the authorization server already trusts, for an access token, with no login screen or user click at that server.

Explainer by Boston Identity, 2026-10-28. 5 min read. https://insights.bostonidentity.com/glossary/jwt-bearer-grant

- What it is: protocol
- Defined by: IETF, RFC 7523 (Standards Track, 2015)
- Who it's for: Teams wiring agents and workloads to APIs

## What is JWT Bearer Grant?

OAuth 2.0 is the framework under which an authorization server issues access tokens to clients [S1 §1]. A JSON Web Token (JWT) is a compact, signed set of statements about a subject. RFC 7523, a Request for Comments from the Internet Engineering Task Force (IETF), lets a client present a JWT at an authorization server's token endpoint as a way to get an access token [S1 §1]. The point is to reuse an existing trust relationship, carried in the JWT, without a direct user-approval step at the authorization server [S1 §1].

The same RFC defines a second, separate use: a client can present a JWT to authenticate itself at the token endpoint [S1 §2.2]. In that case the JWT's subject must be the client's client_id, and a failed check must return the invalid_client error [S1 §3, §3.2]. The RFC says the two uses can be combined or used apart [S1 §1]. The grant is the main subject here.

Think of it like this: It works like a letter of introduction from someone your bank already knows: the bank checks the signature and the date, then opens the account without meeting your referee. The comparison stops at theft, because anyone holding the letter can use it until it expires.

Not the same as: Not the same as token exchange, in which a client posts a subject token and gets back a new token for a named audience [BI-FIND-2020-0004](https://insights.bostonidentity.com/ref/BI-FIND-2020-0004). The JWT bearer grant takes a signed JWT and returns an access token [S1 §1]. The identity-chaining draft runs the two one after the other [BI-FIND-2026-0185](https://insights.bostonidentity.com/ref/BI-FIND-2026-0185).

## How does JWT Bearer Grant work?

Three parties take part: the issuer that signs the JWT, the client that holds it, and the authorization server that issues the access token. The issuer and the server must agree in advance on identifiers, keys and limits, and the RFC leaves that agreement to other documents [S1 §5].

[Figure: The client never shows the authorization server a password: it carries a JWT signed by an issuer the server already trusts, and the server checks the audience, expiry and signature before issuing a token.]

1. **The issuer signs a JWT.** The JWT must carry an issuer, a subject, an audience naming the authorization server, and an expiry time, and the issuer must sign it or apply a message authentication code (MAC) [S1 §3]. For a grant, the subject is typically the resource owner or someone acting for them [S1 §3]. How the client comes to hold the JWT is out of scope [S1 §1].
2. **The client posts it to the token endpoint.** The client sends an access token request with grant_type set to urn:ietf:params:oauth:grant-type:jwt-bearer and the JWT in the assertion parameter, which must hold a single JWT [S1 §2.1]. It may add a scope. Client authentication is optional, so a client_id is needed only when the chosen authentication relies on it [S1 §2.1].
3. **The authorization server checks the JWT.** The server must reject a JWT that lacks its own identity in the audience, has expired, or has an invalid signature or MAC [S1 §3]. It compares issuer and audience values as plain strings unless a profile says otherwise [S1 §3]. It may track JWT IDs to block replays, and if the request carries client credentials it must validate them [S1 §3, §3.1].
4. **The server answers.** A JWT that passes lets the server issue an access token as OAuth 2.0 describes [S1 §3]. A JWT that fails, or falls outside its valid time window, gets an error response whose code must be invalid_grant [S1 §3.1].

## Why does JWT Bearer Grant matter now?

At least one agent design routes identity through this grant. Authors from Anthropic, OpenAI, Okta, Defakto and Ping Identity propose that an authorization server register an agent platform once, then accept agents the platform vouches for through the RFC 7523 grant [BI-FIND-2026-0521](https://insights.bostonidentity.com/ref/BI-FIND-2026-0521). Their stated reason is that agents of one installation now share one credential, which loses attribution of each agent's actions [BI-FIND-2026-0521](https://insights.bostonidentity.com/ref/BI-FIND-2026-0521). The IETF's workload guidance names the same assertion grant as the proposed standard for swapping stored secrets for federation, and calls token exchange or a custom API discouraged [BI-FIND-2026-0507](https://insights.bostonidentity.com/ref/BI-FIND-2026-0507).

In one draft the grant is also the last hop when a request crosses domains. The identity-chaining draft has a client get a signed JWT grant from its home server through token exchange, then redeem it at the other domain's server under RFC 7523 [BI-FIND-2026-0185](https://insights.bostonidentity.com/ref/BI-FIND-2026-0185).

The base RFC is being revised. A working-group draft says a client-authentication JWT must name the server's issuer identifier as its sole audience, and that the token endpoint URL must not be used [BI-FIND-2026-0350](https://insights.bostonidentity.com/ref/BI-FIND-2026-0350). For authorization grants the server may still be named by either value [BI-FIND-2026-0351](https://insights.bostonidentity.com/ref/BI-FIND-2026-0351). We read this as a bigger change for an agent client that finds servers at run time than for a workload that already knows its server [BI-FIND-2026-0353](https://insights.bostonidentity.com/ref/BI-FIND-2026-0353).

## Where does it fit?

- Compared with OAuth Token Exchange: Token exchange posts a subject token, and optionally an actor token, and gets back a new token for a named audience [BI-FIND-2020-0004](https://insights.bostonidentity.com/ref/BI-FIND-2020-0004). The JWT bearer grant takes one signed JWT and returns an access token.
- Compared with OAuth Identity and Authorization Chaining Across Domains: Identity chaining defines no new token; it runs token exchange at home and then the JWT bearer grant at the far domain's server [BI-FIND-2026-0185](https://insights.bostonidentity.com/ref/BI-FIND-2026-0185).
- Compared with OAuth SPIFFE Client Authentication: The SPIFFE client-authentication draft uses a signed JWT in the RFC 7523 family to authenticate a workload to the token endpoint [BI-FIND-2026-0353](https://insights.bostonidentity.com/ref/BI-FIND-2026-0353). That is the client-authentication half of RFC 7523, not the grant.

## What goes wrong?

- The JWT is a bearer credential. The RFC does not mandate replay protection for either use; it calls it an optional feature [S1 §6]. In the agent-platform draft, whoever holds the assertion can redeem it until it expires, and proof of possession and mandatory replay rejection are listed as open issues [BI-FIND-2026-0522](https://insights.bostonidentity.com/ref/BI-FIND-2026-0522).
- The RFC sets no maximum lifetime and no one-time-use rule; both are left to agreement between the parties [S1 §5]. The server only may reject an expiry unreasonably far in the future [S1 §3].
- Client authentication is optional for the grant and left to the server's policy [S1 §3.1]. A server that skips it accepts the JWT from whoever presents it.
- The audience rule in the 2015 text lets a token endpoint URL serve as the audience [S1 §3]. The revision forbids that for client authentication because addresses other than the issuer cannot be validated and can open an attack vector [BI-FIND-2026-0350](https://insights.bostonidentity.com/ref/BI-FIND-2026-0350). A separate draft says that without a countermeasure a malicious server can list an honest server's token endpoint as its own and collect assertions valid there [BI-FIND-2026-1033](https://insights.bostonidentity.com/ref/BI-FIND-2026-1033).
- Nothing in the grant says what the subject may do or how to revoke it. The agent-platform draft never mentions revocation and leaves permissions to the server's local policy [BI-FIND-2026-0522](https://insights.bostonidentity.com/ref/BI-FIND-2026-0522).
- A JWT may carry privacy-sensitive claims, so it should travel only over encrypted channels such as Transport Layer Security (TLS) and carry only the claims needed [S1 §7].

## What should a security leader ask?

1. Which of our authorization servers accept the jwt-bearer grant, and from which issuers?
2. For each trusted issuer, what is the longest JWT lifetime we accept, and do we reject reused JWT IDs?
3. Does our server require client authentication alongside a JWT grant, or will it redeem a JWT from anyone who presents it?
4. Do our clients name the server's issuer identifier as the sole audience in client-authentication JWTs, or the token endpoint URL?
5. If an agent platform we trust is compromised, how do we stop its signed JWTs from being redeemed before they expire?

## Sources

- [S1] [JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization Grants](https://www.rfc-editor.org/rfc/rfc7523.txt) (IETF, RFC 7523, Standards Track, May 2015)

## Evidence

- [BI-FIND-2020-0004](https://insights.bostonidentity.com/ref/BI-FIND-2020-0004): Every delegation design in this corpus reduces to one grant type from a January 2020 RFC written for services, by engineers at Microsoft, Ping Identity, Yubico and Visa, that never mentions an agent. The standard defines an HTTP and JSON security token service: a client posts a subject token and, optionally, an actor token to the token endpoint and receives a new token for a named audience, with typed token identifiers so a SAML assertion can be traded for a JWT. The transaction-tokens draft mints its token through this exchange, the identity-chaining draft runs it before a JWT bearer grant to cross domains, Uber's exchange is conceptually based on it and its builder says the newer standards are not ready to implement as written, and the working group's agent draft composes it rather than replacing it. The agent-specific work is all profile; the base has not changed in six years. (from "The token exchange RFC that agent designs cite says its record of earlier actors is not for access decisions")
- [BI-FIND-2026-0185](https://insights.bostonidentity.com/ref/BI-FIND-2026-0185): Chaining defines no new token. A client in domain A takes the token it already holds to its own authorization server and, through RFC 8693 token exchange, receives a signed JWT grant whose audience is one authorization server in domain B; it presents that grant there under RFC 7523's JWT-bearer profile and gets a domain-B access token. The precondition is arranged in advance: B trusts A's signing keys, typically through A's published key set. The audience 'is restricted to a single authorization server in trust domain B to prevent an authorization server from presenting the client's authorization grant to an authorization server in a different trust domain', so a grant cannot be relayed on to a domain C. Uber's production exchange is 'conceptually based on' the first of those RFCs; ZeroID's delegation engine is built on it; the draft shows what the second RFC adds when the far end is someone else's server. (from "The cross-domain OAuth draft is one step from an RFC, and it never mentions agents")
- [BI-FIND-2026-0521](https://insights.bostonidentity.com/ref/BI-FIND-2026-0521): Authors from Anthropic, OpenAI, Okta, Defakto and Ping Identity propose that an authorization server register an agent platform once and then accept any agent that platform vouches for. The platform signs a JWT naming one agent by an opaque identifier that is never reassigned; the agent presents it through the existing RFC 7523 JWT-bearer grant, and the server accepts a subject it has never seen as long as the issuer matches one registration and the signature checks under that registration's keys. A server "MUST NOT require a client registration per Agent". The stated reason is what happens today: every agent of an installation shares one credential, "at the cost of any attribution of an individual agent's actions". (from "Authors from Anthropic, OpenAI, Okta and Ping want the agent platform registered once, not every agent")
- [BI-FIND-2026-0507](https://insights.bostonidentity.com/ref/BI-FIND-2026-0507): The working group's recommended pattern replaces stored secrets with federation: the platform issues the workload a signed JWT, the workload presents it to an identity provider, and gets back an access token. The JWT "MUST" name that provider as its sole audience, a token for the Kubernetes API must not be reused anywhere else, and credentials must not sit in environment variables where the platform offers a file or local API. Appendix A names the assertion grant (RFC 7521 and the rfc7523bis update, typ authorization-grant+jwt) as the proposed standard for the exchange and calls token exchange or a custom API "discouraged as they prevent interoperability". (from "IETF workload guidance swaps stored secrets for a single-audience JWT and advises against custom token exchange")
- [BI-FIND-2026-0350](https://insights.bostonidentity.com/ref/BI-FIND-2026-0350): A JWT used to authenticate an OAuth client now has exactly one permitted audience. The draft rewrites RFC 7523's rule so that the audience 'MUST use the issuer identifier [RFC8414] of the authorization server as its sole value', that 'the token endpoint URL of the authorization server MUST NOT be used as an audience value', and that the server 'MUST reject any JWT that does not contain its issuer identifier as its sole audience value', compared by simple string comparison. Pushed authorization requests get the same rule. The reason given is that endpoint addresses other than the issuer cannot be validated and, sent to a different endpoint, 'can open an attack vector'; the attack itself is the audience-injection class University of Stuttgart researchers disclosed in January 2025. (from "The JWT an agent or other OAuth client signs in with may name only the server's issuer, never the token endpoint")
- [BI-FIND-2026-0351](https://insights.bostonidentity.com/ref/BI-FIND-2026-0351): The strictness stops at client authentication. For assertion-based authorization grants the server 'MAY be identified by either its issuer identifier or its token endpoint URL', a mandate the working group dropped at revision -02 to limit breakage, and a SAML grant may also name a SAML entity identifier. The other change is a closure: 'SAML Bearer Assertions MUST NOT be used for client authentication for any new applications', with existing deployments left to each operator. Explicit typing of the client-authentication JWT is a SHOULD, not a MUST, and servers are told it is 'NOT RECOMMENDED' to reject untyped JWTs. (from "The JWT an agent or other OAuth client signs in with may name only the server's issuer, never the token endpoint")
- [BI-FIND-2026-0353](https://insights.bostonidentity.com/ref/BI-FIND-2026-0353): Nothing in the draft is about AI agents or workloads, and all of them are downstream of it. The SPIFFE client-authentication draft and the client-attestation draft both authenticate a non-human client to the token endpoint with a signed JWT in the RFC 7523 family, and the metadata-document draft that the Model Context Protocol adopted requires key-based client authentication of the same kind. Each of those will now be read against an audience rule that names the issuer identifier and nothing else, which is a smaller change for a workload that already knows its server than for an agent client that discovers servers at run time and must mint one assertion per issuer. (from "The JWT an agent or other OAuth client signs in with may name only the server's issuer, never the token endpoint")
- [BI-FIND-2026-0522](https://insights.bostonidentity.com/ref/BI-FIND-2026-0522): The grant identifies the agent and does little to hold it. The assertion is a bearer credential and client authentication is optional, so whoever holds it can redeem it until it expires; proof of possession, an explicit token type and mandatory replay rejection by jti are all listed as open issues. The text never mentions revoking an agent, a platform registration or an issued token. Short lifetimes and no refresh tokens are the only brakes. What the agent may do is the server's local policy, optionally mapped from claims the platform asserts, and is declared out of scope. (from "Authors from Anthropic, OpenAI, Okta and Ping want the agent platform registered once, not every agent")
- [BI-FIND-2026-1033](https://insights.bostonidentity.com/ref/BI-FIND-2026-1033): For audience injection, revision -01 puts the duty on the client. A client that works with more than one authorization server and authenticates with signed assertions "MUST employ one of the following countermeasures, unless audience injection attacks are mitigated by other means, such as using fresh key material for each authorization server": the server's issuer identifier as the assertion's sole audience, or the exact endpoint URI it is sent to. Without one, a malicious server can list an honest server's token endpoint as its own, and an assertion the client sends to the attacker's pushed authorization, revocation, CIBA or device endpoint is valid at the honest server. The draft calls that endpoint list not exhaustive, covers private_key_jwt and SAML assertions as well as RFC 7523 JWTs, and says the countermeasures need no normative change on the server side. (from "An OAuth client brokering many tools, as agent services do, can let a rogue tool take over a user's other tools")

---

© 2026 Boston Identity LLC. All rights reserved. Published by Boston Identity LLC.
Quote up to 100 words with the credit "Boston Identity, IAM Insights" and a link to https://insights.bostonidentity.com/glossary/jwt-bearer-grant. Claim numbers may be cited freely. Training, fine-tuning and text-and-data-mining use of this page is permitted.
Terms: https://insights.bostonidentity.com/terms · How to cite: https://insights.bostonidentity.com/cite
