Delegate SD-JWT
dSD-JWT · dSD-JWT+KB · Delegated SD-JWT · draft-gco-oauth-delegate-sd-jwt · draft-gco-oauth-delegate-sd-jwt-00
An Internet-Draft that lets the holder of a Selective Disclosure JSON Web Token (SD-JWT) delegate it onward, so a verifier can walk the chain back to the issuer.
Where it stands
WG adopted since Oct 30, 2026.
Checked Nov 22, 2026.
In our briefings
What our briefings say about Delegate SD-JWT itself, with the most direct claims first.
The part a verifier has to implement, checking that a closed mandate was derived from the open one a person signed, is delegated to a text the page cites and does not define: "Verify and process the SD-JWT chain according to Delegate SD-JWT", an individual draft by G. Oliver dated 2026. What the page itself fixes is the shape: an open mandate carries constraints and the agent's key as cnf, a closed one is bound to a transaction through a key-binding JWT, the verifier confirms the closed content keeps the open claims and satisfies every constraint, an unknown constraint must fail, and the verifier must return a signed Mandate Receipt whose reference is a hash of the final token. When a mandate holds selective disclosures, the agent must choose the ones that maximize the person's privacy while still providing authorization. Receipts reduce the open mandate's scope on the agent's side only; nothing lets a verifier or a person revoke an open mandate once issued.
Google's AP2 authorization companion lets a verifier trust a credential issuer or the agent's provider, and names no trust list or revocationBI-FIND-2026-0436
›Cited in 10 briefings
Every briefing that discusses this term, newest first.
- Verifiable Intent stops an AI agent from passing its buying authority on, and v0.1 has no protocol to revoke it
Article · · Verifiable Intent (GitHub, agent-intent/verifiable-intent) · Verifiable Intent Working Group · Apr 18, 2026
- OAuth's token revocation list nears RFC, and a shared list hides which token is checked
Draft · · IETF Datatracker · Tobias Looker et al. · Aug 13, 2026
- A Nokia and China Mobile draft finds A2A and MCP stop at one hop, and wants cancellation carried down the chain
Draft · · IETF Datatracker · Tirumaleswar Reddy.K et al. · Oct 27, 2026
- Sweeney's delegation draft concedes its server is trusted with users' credentials, and drops an interop claim
Draft · · IETF Datatracker · Kieran Sweeney · Oct 13, 2026
- OAuth adopts Delegate SD-JWT, which traces each hand-off to the issuer but never checks that authority narrowed
Draft · · IETF Datatracker · Gareth Oliver et al. · Apr 22, 2026
- The SD-JWT standard that agent drafts build on never mentions agents and leaves key binding to each verifier
Article · · IETF (RFC Editor) · Daniel Fett et al. · Nov 20, 2025
- A draft ties what each AI agent may read to what it may do, and still can't take a grant back
Draft · · IETF Datatracker · Hamdy Atakora · Sep 21, 2026
- Cisco's SD-Card puts an A2A Agent Card in a selective-disclosure token, and leaves its registry out of scope
Draft · · IETF Datatracker · Suhas Nandakumar et al. · Mar 2, 2026
- Google's AP2 authorization companion lets a verifier trust a credential issuer or the agent's provider, and names no trust list or revocation
Article · · ap2-protocol.org · Google · Apr 28, 2026
- OpenID4VP 1.0 makes verifiers re-check what a wallet returns, and cannot show a holder acting for someone else
Article · · OpenID Foundation · Oliver Terbu et al. · Jul 9, 2025
Related terms
What appears alongside Delegate SD-JWT in the same briefings.