# What is OAuth Identity and Authorization Chaining Across Domains?

> A way to carry who a user is, and what they allowed, from one organization's OAuth system into another's. The home server issues a signed grant; the far server swaps it for its own access token.

Explainer by Boston Identity, 2026-10-17. 6 min read. https://insights.bostonidentity.com/glossary/identity-chaining

- What it is: protocol
- Defined by: IETF OAuth working group draft (-17), approved and waiting at the RFC Editor
- Who it's for: Teams whose agents or services call APIs in another organization

## What is OAuth Identity and Authorization Chaining Across Domains?

OAuth (the open standard for delegated access to APIs) works well inside one trust domain, the set of systems that answer to one authorization server. A request often has to go further. Every service on the path needs to know which user started the request and what that user allowed [S1 §1]. Identity and Authorization Chaining Across Domains is the Internet Engineering Task Force (IETF) draft that keeps that information intact when a request crosses into another organization's systems [S1 §1].

It defines no new token. It combines two published standards: token exchange (RFC 8693), done at home, and the JSON Web Token (JWT) bearer grant (RFC 7523), used at the far side [S1 §2]. A home system may hand out the grant through its own interface instead of token exchange [S1 §2]. Each crossing repeats the same steps, so the pattern can run through several domains in turn [S1]. It is a draft, not yet a standard. The datatracker showed revision 17 approved and waiting only for the RFC Editor [BI-FIND-2026-0184](https://insights.bostonidentity.com/ref/BI-FIND-2026-0184).

Think of it like this: Think of a letter of introduction. Your own bank writes and signs it for one named foreign bank, and that bank then opens a local account for you. The comparison stops at risk: anyone who holds this letter can use it, so the draft suggests limits such as a short life or a single use.

Not the same as: Not the same as plain token exchange, which trades one token for another at a single authorization server. Chaining normally uses that exchange at home only to get a grant that a different organization's server will accept.

## How does OAuth Identity and Authorization Chaining Across Domains work?

Four parties take part. A client in domain A holds a token from its own authorization server, and it wants a resource behind domain B's authorization server. Domain B already trusts domain A's signing keys [S1 §2.1].

[Figure: The client trades its domain A token for a signed grant at home, swaps that grant for domain B's access token, then calls the resource.]

1. **The client finds domain B's server.** The client works out which authorization server guards the resource in domain B. It may read the resource's published metadata (RFC 9728), keep a fixed mapping, or use other means [S1 §2.2].
2. **The client asks its home server for a grant.** The client sends the token it already holds to domain A's authorization server as an RFC 8693 token exchange. The request must name domain B's server, by its address or by a logical name. The client may also ask for a narrower scope [S1 §2.3.1].
3. **Domain A's server issues a signed grant.** Domain A's server must refuse if the target is unknown or its policy says no [S1 §2.3.2]. Otherwise it returns a JWT authorization grant, signed with its own key [S1 §2.1]. The grant's audience, the server it is meant for, must name domain B's server. The draft recommends naming only one, so domain B cannot pass the grant on to a third domain [S1 §2.3.3].
4. **The client presents the grant to domain B.** The client sends the grant to domain B's token endpoint as a JWT bearer assertion under RFC 7523 [S1 §2.4.1]. It can say which resource it wants with the scope or resource parameter.
5. **Domain B's server checks it and issues a token.** Domain B's server validates the grant's signature and audience against the keys it trusts for domain A [S1 §2.1]. It must deny the request if it cannot identify the subject, the user the grant is about. It may also deny it on policy, such as no trust relationship with domain A [S1 §2.4.2]. If all is well, it returns its own access token [S1 §2.4.3].
6. **The client calls the resource.** The client uses domain B's access token to call the protected resource in domain B [S1 §2.1].

## Why does OAuth Identity and Authorization Chaining Across Domains matter now?

Agents now cross company lines. A vendor's agent may act on a customer's data, and other agent work points at this draft for that case. The transaction-tokens draft keeps its tokens inside one trust domain and hands the crossing to identity chaining [BI-FIND-2026-0174](https://insights.bostonidentity.com/ref/BI-FIND-2026-0174). The six-vendor agent draft names it for agent parts that sit behind different authorization servers [BI-FIND-2026-0184](https://insights.bostonidentity.com/ref/BI-FIND-2026-0184). The workload identity architecture (WIMSE) also sends a workload out of its home domain by this pattern. Its alignment section there still reads as a to-do [BI-FIND-2026-0300](https://insights.bostonidentity.com/ref/BI-FIND-2026-0300).

Of the standards in that conversation, this one is nearest to done. We forecast that the RFC Editor publishes it with an RFC number by 31 March 2027 [BI-CALL-2026-0055](https://insights.bostonidentity.com/ref/BI-CALL-2026-0055). Okta and Ping Identity each have an author on it [BI-FIND-2026-0184](https://insights.bostonidentity.com/ref/BI-FIND-2026-0184).

The crossing is where a customer can narrow a vendor's agent. Either server may add, remove or remap claims. A client may ask for less, and the server checks that the scopes it asks for are no wider than the token it presented [BI-FIND-2026-0186](https://insights.bostonidentity.com/ref/BI-FIND-2026-0186). A newer profile for transaction tokens copies this design. Each server keeps its output no wider than its input, one crossing at a time [BI-FIND-2026-0494](https://insights.bostonidentity.com/ref/BI-FIND-2026-0494).

## Where does it fit?

- Compared with OAuth Token Exchange: Token exchange is one step at one server. Chaining uses it at the home server to get a grant aimed at a foreign server, then adds a second step there.
- Compared with JWT Bearer Grant: The JWT bearer grant is how domain B accepts a signed assertion. The chaining draft describes getting that assertion by token exchange at domain A's server, and it does not rule out other ways.
- Compared with Transaction Tokens: Transaction tokens carry context between services inside one trust domain and stop at its edge. Chaining is the sibling draft that handles the crossing between domains.
- Compared with Identity Assertion Authorization Grant: ID-JAG (the identity assertion JWT authorization grant) is a profile that starts from a person's single sign-on assertion at an identity provider both sides trust. It and a newer transaction-token profile are sibling grants built on the chaining framework [BI-FIND-2026-0496](https://insights.bostonidentity.com/ref/BI-FIND-2026-0496).

## What goes wrong?

- The grant is a bearer token, so anyone who steals it can replay it at domain B. The draft lists short lifetimes, single use and client authentication as mitigations, and domain B's server can enforce them [S1 §5.5].
- Authorization servers should sender-constrain tokens as the OAuth security best practice (RFC 9700) advises. The draft admits that bearer tokens are still the most widely deployed kind [S1 §5.2].
- A stolen home token could become a lateral move into domain B. Domain A's server can check that the client is allowed to present that token before issuing a grant. The draft recommends this check where it can be run [S1 §5.3].
- Domain B should not issue refresh tokens to the client. A refresh token would let the client keep getting access after the user logs out or loses access in domain A [S1 §5.4].
- The draft does not define the format of transcribed claims [S1 §2.5]. One proposal offers a delegation chain for that gap, but it gives two accounts of who signs the earlier records [BI-FIND-2026-1289](https://insights.bostonidentity.com/ref/BI-FIND-2026-1289).
- The draft carries which resource servers were called earlier only as an option [S1 §2.5]. Beyond that option, nothing in the token says who acted in between, and nothing extends per hop [BI-FIND-2026-0187](https://insights.bostonidentity.com/ref/BI-FIND-2026-0187). One implementer found the draft silent on a subject token with no subject claim [BI-FIND-2026-0894](https://insights.bostonidentity.com/ref/BI-FIND-2026-0894).

## What should a security leader ask?

1. Which of our partners' authorization servers trust our signing keys today, and who approved each one?
2. When a vendor's agent reaches our data, does our authorization server narrow its scope and claims, or pass everything through?
3. Do the grants we issue name a single audience and expire within minutes, and can each be used only once?
4. Does any partner domain issue refresh tokens on a chained grant, so access outlives the user's session with us?
5. If a request crosses three domains, how would we trace which service acted at each hop?

## Sources

- [S1] [OAuth Identity and Authorization Chaining Across Domains](https://datatracker.ietf.org/doc/html/draft-ietf-oauth-identity-chaining-17) (IETF OAuth working group, Internet-Draft, revision 17 (19 July 2026))

## Evidence

- [BI-FIND-2026-0184](https://insights.bostonidentity.com/ref/BI-FIND-2026-0184): Of every standard the agent-identity conversation points at, this is the one nearest to done. The datatracker shows draft-ietf-oauth-identity-chaining at revision 17, Standards Track, IESG state 'RFC Ed Queue': approved, waiting only for the RFC Editor. The authors are Arndt Schwenkschuster and Pieter Kasselman of Defakto, Kelley Burgin of MITRE, Mike Jenkins of the NSA's commercial cybersecurity arm, Brian Campbell of Ping Identity and Aaron Parecki of Okta, and the consensus is tighter than the list suggests: Campbell co-wrote both RFCs this draft combines, and Parecki co-wrote the discovery RFC it uses to find the other domain. The transaction-tokens draft names it as the cross-domain mechanism, and the six-vendor agent draft names it for the case where an agent's components sit behind different authorization servers. Both of those are further from publication than this. (from "The cross-domain OAuth draft is one step from an RFC, and it never mentions agents")
- [BI-FIND-2026-0174](https://insights.bostonidentity.com/ref/BI-FIND-2026-0174): A transaction token is valid inside one trust domain and stops at its edge. Crossing into another domain is handed to a sibling draft, OAuth Identity and Authorization Chaining Across Domains, which Kasselman also co-authors, so the two are designed to interlock: transaction tokens inside, identity chaining between. For the case the summit's Aembit CEO called the hard half, an agent that runs inside a SaaS vendor's product and acts on a customer's data, this draft therefore offers nothing directly. The vendor's domain and the customer's are two trust domains, and the token that would carry the customer's user and authorization context across that boundary is the chaining draft's job, which nobody in our corpus has yet read. (from "OAuth's transaction token goes unchanged down a service chain and names who started it, not who acted in between")
- [BI-FIND-2026-0300](https://insights.bostonidentity.com/ref/BI-FIND-2026-0300): A WIMSE identity is local by design, and the way out of the local domain is unfinished. Identifiers are scoped to a trust domain, and credentials 'constrain the subjects and actors identified in delegation and impersonation tokens to be bound by a trust domain'. To reach another organization a workload trades its credential at a token service for one the other side's token service will accept, following the OAuth identity-chaining pattern, and the section that should align the two still reads '(TODO: align with OAuth cross domain identity and authorization)'. An agent hosted by one company and acting inside another is the case this leaves open. (from "The IETF's workload-identity architecture gives AI agents one subsection, calling an agent a delegated workload")
- [BI-CALL-2026-0055](https://insights.bostonidentity.com/ref/BI-CALL-2026-0055): By 31 March 2027 the RFC Editor publishes OAuth Identity and Authorization Chaining Across Domains as an RFC with a number. The draft is already past the IESG and in the editor's queue, and the queue's normal residence is a few months. Wrong if on that date the datatracker still shows an IESG state rather than an RFC number, or the document has been returned to the working group. (from "The cross-domain OAuth draft is one step from an RFC, and it never mentions agents")
- [BI-FIND-2026-0186](https://insights.bostonidentity.com/ref/BI-FIND-2026-0186): The interesting work happens at the crossing, and the draft gives the receiving side the pen. Authorization servers on either side of the hop may add, remove or remap claims: a subject identifier that differs between domains is rewritten; a bank's server strips 'account type: premium' and passes only a transaction limit, so 'domain B receives only the claims relevant to its operations'; and a client may ask for less, with the server checking that 'the requested scopes are not higher privileged than the scopes of the presented subject_token'. That is the transaction-tokens draft's never-wider rule applied across a boundary, and it is where a customer's own authorization server would narrow a SaaS vendor's agent before it touched anything. The draft then leaves the claim format and the transcription mechanics undefined, which is the gap any implementation will fill on its own terms. (from "The cross-domain OAuth draft is one step from an RFC, and it never mentions agents")
- [BI-FIND-2026-0494](https://insights.bostonidentity.com/ref/BI-FIND-2026-0494): Narrowing is a no-wider rule that authorization servers check one crossing at a time. Domain A's server "MUST NOT" issue a grant broader than the Txn-Token's scope (the grant's scope is the intersection of the token's and the request's), and domain B's server must independently keep its access token within the grant. Applied across three or more domains, each crossing is self-contained under its own bilateral trust agreement: nothing ties the third hop back to the first, the draft concedes a grant's claims may derive from what an upstream domain sent, and only scope strings narrow, with rich authorization details left to a later revision. (from "A cross-domain transaction-token grant names who started the transaction and drops the agent that asked")
- [BI-FIND-2026-0496](https://insights.bostonidentity.com/ref/BI-FIND-2026-0496): If adopted, OAuth's cross-domain toolkit would carry two sibling JWT grants built on the same chaining framework. ID-JAG starts from a person's single sign-on assertion at an identity provider both sides trust; this one starts from a Txn-Token, covers people, systems and workloads, and rests on a bilateral agreement instead of a shared provider, with no client_id, tenant claims or authorization details. A server running both tells them apart by the typ header. The OAuth list already has a thread titled after a direct ID-JAG-to-Txn-Token exchange (Issue #17), a step this -00 does not contain. (from "A cross-domain transaction-token grant names who started the transaction and drops the agent that asked")
- [BI-FIND-2026-1289](https://insights.bostonidentity.com/ref/BI-FIND-2026-1289): Across trust domains, the draft offers delegation_chain as the form for the claims transcription that the OAuth working group's identity-chaining draft leaves undefined, and the receiving server MUST copy the chain into the token it issues. It then gives two accounts of who signs the upstream records. Section 8.3 has resource servers verify each record with the key of the server that issued it, which "may differ across records"; section 10.7 says the receiving server re-signs the upstream records, so every record verifies with the current issuer's key. We read these as two different tokens, and the draft does not say which a resource server should expect. (from "A June OAuth draft logs each hand-off between AI agents, but the per-hop limits the act claim lacks are optional")
- [BI-FIND-2026-0187](https://insights.bostonidentity.com/ref/BI-FIND-2026-0187): The draft's appendix answers part of the question Uber left open, for the cross-domain case and without saying 'agent'. A resource server may act as the client, discovering the other domain's authorization server from that domain's own protected-resource metadata; and an authorization server may act as the client for callers that cannot reach the other domain themselves, so that 'an authorization server in trust domain A may obtain an access token from an authorization server in trust domain B on-behalf-of any client in trust domain A'. Delegated key binding carries the original client's key across in a requested_cnf parameter so the resulting token stays bound to it. That is a standards-track description of an intermediary carrying authority across a boundary on a client's behalf, which is what an agent gateway is sold as. What it does not carry is an actor chain: nothing in the token says who acted in between, and nothing extends per hop. Medium, because the relevance to agents is ours and the draft's own use cases are CI pipelines, partner dashboards and cross-domain calendars. (from "The cross-domain OAuth draft is one step from an RFC, and it never mentions agents")
- [BI-FIND-2026-0894](https://insights.bostonidentity.com/ref/BI-FIND-2026-0894): The identity-chaining draft, already approved and waiting at the RFC Editor, is silent on a subject token that carries no sub claim. Agnihotri's server issues the chaining grant anyway and refuses it only when it is presented, which he calls allow and defer, and he proposes text letting a server either synthesise a subject or refuse, with refusal recommended. Both gaps in the report come from one implementation with no interoperability testing, and the author says so. (from "One implementer found a transaction-token rule that let any scope through; the OAuth group fixed it in weeks")

---

© 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/identity-chaining. 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
