# What is Resource Indicators for OAuth 2.0?

> An OAuth extension that lets an app tell the token issuer which service it will use a token at, so the issuer can make a token that works only there and not at every service it protects.

Explainer by Boston Identity, 2026-10-28. 6 min read. https://insights.bostonidentity.com/glossary/resource-indicators

- What it is: protocol
- Defined by: IETF, RFC 8707 (Standards Track)
- Who it's for: Teams connecting agents and apps to APIs

## What is Resource Indicators for OAuth 2.0?

Resource indicators are one request parameter, named resource, added to OAuth 2.0, the open standard apps use to get access tokens for APIs on a person's behalf [S1 §2]. With it, a client (the app asking for access) tells the authorization server (the service that issues tokens) which protected resource it means to use the token at [S1 Abstract]. The value must be an absolute URI, typically a web address such as https://api.example.com/app/, though it can also be a more abstract identifier [S1 §2].

The problem it solves is a token that works in too many places. Most OAuth access tokens are bearer tokens: anyone holding one can use it [S1 §1]. Scope, the older OAuth field, usually says what kind of access is wanted, such as "calendar" or "admin:org", and not where the token will be redeemed [S1 §1]. Once the authorization server knows the destination, it can restrict the token's audience, the service the token is for, so it fails at other resources [S1 §1]. The authors note that several deployments had already built their own parameters for this, and the RFC aims to offer one shared alternative [S1 §1].

Think of it like this: It is like a cheque made out to a named payee instead of to cash: the bank pays only that payee. The comparison breaks at enforcement: the issuer should write the payee in, but nothing works unless the receiving service checks it.

Not the same as: Not the same as scope, which says what the client may do. The resource parameter says where it may do it, and a request can carry both [S1 §2.2].

## How does Resource Indicators for OAuth 2.0 work?

Three kinds of actor take part: a client, the authorization server that issues tokens, and the protected resources, here a calendar API and a contacts API taken from the RFC's own examples [S1 §2.1].

[Figure: The client names both APIs up front, then takes a calendar-only token and later trades its refresh token for a contacts-only one, so neither token works at the other service.]

1. **The client names the resources it wants.** In its authorization request the client may add one resource parameter per service, for example the calendar and the contacts APIs together [S1 §2.1, Figure 2]. Each value must be an absolute URI with no fragment, and should not carry a query string unless the application needs one [S1 §2]. The client should use the most specific address it can, usually the base address of the API [S1 §2].
2. **The authorization server checks the request.** If the server cannot parse a value or will not accept it, it should reject the request with the error invalid_target [S1 §2.1]. If the client leaves the parameter out, the server may go ahead with no resource or a default one, or it may require the parameter and fail the request [S1 §2.1]. In the code flow, the named resources apply to the whole grant the authorization code stands for [S1 §2.1].
3. **The client asks for a token for one resource.** At the token endpoint the client sends the resource parameter again, now naming where it will use this particular token, such as the calendar alone [S1 §2.2, Figure 3]. This works for every grant type [S1 §2.2]. Which values the server accepts is up to its local policy, and it may limit them to what the resource owner originally granted [S1 §2.2]. When an authorization code is exchanged for a token covering only some of the granted resources, any refresh token returned stays bound to the full original grant [S1 §2.2].
4. **The authorization server mints an audience-restricted token.** The server should restrict the token's audience to the named resource, for example in the aud claim of a JSON Web Token (JWT) [S1 §2]. It may use the exact resource value as the audience, or map it to a broader identifier [S1 §2]. Where it can, it should also downscope, giving the token only the scope that service needs, and it reports the effective scope when that differs from the request [S1 §2.2, Figure 4].
5. **The client refreshes for the next resource.** Later the client sends its refresh token with a different resource value, the contacts API, and gets a separate token for that service with the contacts scope [S1 §2.2, Figures 5 and 6].

## Why does Resource Indicators for OAuth 2.0 matter now?

The Model Context Protocol (MCP), which connects AI agents to tools, made this parameter mandatory in its 2026-07-28 authorization specification [BI-FIND-2026-0191](https://insights.bostonidentity.com/ref/BI-FIND-2026-0191). MCP clients must send a resource parameter naming the server's canonical address on every authorization and token request, and MCP servers must validate the audience of every token [BI-FIND-2026-0191](https://insights.bostonidentity.com/ref/BI-FIND-2026-0191). We read that as ruling out the token-passthrough gateway: under the specification, a proxy that hands a person's token on to the tools behind it is out of bounds [BI-FIND-2026-0191](https://insights.bostonidentity.com/ref/BI-FIND-2026-0191).

At least one vendor has it in beta. Cisco Duo added resource indicators to a beta MCP integration, so an agent can name the resource it wants and get a token valid only there [BI-FIND-2026-1194](https://insights.bostonidentity.com/ref/BI-FIND-2026-1194). Duo's Medfisch says this keeps a token for one service from being replayed at another [BI-FIND-2026-1194](https://insights.bostonidentity.com/ref/BI-FIND-2026-1194).

The parameter does not settle everything for agents. One arXiv author, Liu, argues that OAuth does not say how a provider's canonical resource should override a resource string the caller supplies [BI-FIND-2026-1270](https://insights.bostonidentity.com/ref/BI-FIND-2026-1270). That is one paper with an in-memory prototype, so we hold it at low confidence [BI-FIND-2026-1270](https://insights.bostonidentity.com/ref/BI-FIND-2026-1270).

## Where does it fit?

- Compared with JWT Profile for OAuth 2.0 Access Tokens: Resource indicators shape the client's request to the issuer. The audience they produce ends up inside the issued token, in the aud claim when the token is a JWT [S1 §2], and the layout of that token is a separate question from this RFC.
- Compared with OAuth Token Introspection: Resource indicators set a token's audience when it is issued. Introspection is a separate exchange, and its response carries that same audience in a top-level aud member [S1 §2].

## What goes wrong?

- A token with several audiences is valid at each of them, so any one of those services can use it to reach the others. The RFC encourages a single resource per request and says multi-audience tokens need a high degree of trust between the parties [S1 §3].
- On multi-tenant or user-content hosts, a resource value that leaves out the tenant's part of the address lets one tenant's token work against another tenant's data [S1 §3].
- An abstract identifier instead of a real address shifts work to the client, which must check out of band that the endpoint it sends tokens to is the intended audience [S1 §3]. A network address lets the client check that directly, which lowers the risk of a malicious endpoint collecting tokens meant for another service [S1 §3].
- The parameter is optional in the RFC, and audience restriction is a should, not a must [S1 §2]. Protection exists only where the issuer restricts the audience and the resource checks it; MCP narrows that gap: its clients must name the resource and its servers must validate each token's audience [BI-FIND-2026-0191](https://insights.bostonidentity.com/ref/BI-FIND-2026-0191).
- Naming several resources and several scopes in one request asks for a token with every scope usable at every resource, which the RFC calls a cartesian product [S1 §2.2]. The server should downscope each token to what its service needs [S1 §2.2].
- The resource parameter may let the authorization server track a user's behaviour in finer detail than before [S1 §4].

## What should a security leader ask?

1. Does our authorization server reject token requests that omit the resource parameter, or does it quietly issue a token with a default audience?
2. Which of our APIs check the aud claim on every token, and which accept any valid token from our issuer?
3. Do any of our gateways or MCP proxies pass a user's token on to the services behind them?
4. Where we host tenants on one domain, does each resource value include the tenant's part of the address?
5. Which of our clients request tokens for more than one resource at a time, and do those services trust each other enough for that?

## Sources

- [S1] [Resource Indicators for OAuth 2.0](https://www.rfc-editor.org/rfc/rfc8707) (IETF, RFC 8707, Standards Track, February 2020)

## Evidence

- [BI-FIND-2026-0191](https://insights.bostonidentity.com/ref/BI-FIND-2026-0191): The specification binds every token to one server and forbids passing it on. Clients MUST send a resource parameter naming the server's canonical URI on every authorization and token request, and MUST check the issuer on every authorization response, the two controls against mix-up attacks. Servers MUST validate the audience of every token and 'MUST NOT accept or transit any other tokens'. Tokens travel only in the Authorization header, refresh tokens stay confidential and are never assumed, and offline access should not be advertised. That is the same anti-pattern the six-vendor agent draft names, a tool forwarding the token it received, and it is the rule a token-passthrough gateway breaks: a proxy that hands a person's token to the tools behind it is out of specification, whatever the vendor calls it. (from "MCP's authorization spec makes the agent a plain OAuth client and leaves delegation to an extension")
- [BI-FIND-2026-1194](https://insights.bostonidentity.com/ref/BI-FIND-2026-1194): Cisco Duo added two OAuth standards to a new beta integration for the Model Context Protocol (MCP) and to its OAuth 2.1/OIDC integration, also in beta, to match the MCP specification released on November 25. Dynamic client registration (RFC 7591) lets agents register themselves as OAuth clients, and Duo says admins keep full control over the access level of clients registered that way. Resource indicators (RFC 8707) let an agent name the resource it wants so Duo issues a token valid only there, which Medfisch says ensures a token for one service "cannot be replayed or accepted by another." Client ID metadata documents are not in the beta: Medfisch calls them "the future" and says Duo is building support, with no date. (from "Cisco Duo's MCP beta lets agents register themselves; Duo calls client ID metadata documents the future")
- [BI-FIND-2026-1270](https://insights.bostonidentity.com/ref/BI-FIND-2026-1270): Liu wants this execution layer to sit next to OAuth. In Liu's reading, OAuth does not specify how a local agent runtime should bind a file handle to a principal, how a provider's canonical resource should override a resource string the caller supplies, or how a denied data-pipe attempt should be recorded as audit evidence, and "a realistic deployment would need both layers." The paper answers those gaps with HCP's own rules and proposes no change to OAuth. Its prototype keeps grants and audit records in memory, with no provider attestation. (from "In one author's MCP benchmark, a confirmation prompt on every call still let 6 of 10 attacks through")

---

© 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/resource-indicators. 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
