IETF · 30 August 2026
draft-mishra-oauth-agent-grants-02
S. Kumar (Orchestrum Technologies LLP)
If your constraint is 'we will not deploy a new protocol, only profile OAuth', this is the checklist.
At a glance
Actors
01
AI agents invoking APIs on behalf of users need a profile: identify the agent instance, get consent, issue resource-bound sender-constrained tokens, attenuate via token exchange, rotate refresh tokens — without new JWT claims or endpoints. If your constraint is 'we will not deploy a new protocol, only profile OAuth', this is the checklist.
Positions itself as a profile, not a rival to AAuth. Cross-domain hops should use identity chaining rather than private formats.
02
Agent is an OAuth client instance. User is the resource owner. AS and RS are standard. No new parties. Grantex is an incomplete reference implementation and is not required for conformance.
03
draft-mishra-oauth-agent-grants-02, 30 August 2026 (catalog previously said only '2026'), expires 3 March 2027, author S. Kumar (Orchestrum Technologies LLP) despite the 'mishra' filename. PAR + PKCE + resource indicators + JWT access tokens + PoP + RFC 8693 attenuation with act. No new endpoints, no new JWT claims.
04
Flow 1
Identify the agent client instance (pre-register, CIMD, or DCR).
PAR + PKCE + resource=API. User consents.
AS issues audience-restricted, sender-constrained at+jwt (DPoP or mTLS).
Downstream hops: token exchange with nested act, attenuated scope. Never expand.
05
Mostly authorization, using existing OAuth identity of the user plus client identity of the agent. Not a new identity system.
06
Attenuation and OBO.
Front-channel hygiene.
Code binding.
Audience.
Cross-domain instead of private formats.
Rival thesis: this profile stays in OAuth; AAuth does not.
07
The draft says the reference implementation is non-normative and incomplete.
The point of this draft is not to mint aap_* fields. If you need structured agent claims, look at AAP — and compare carefully.
08
Individual informational draft-02, 30 August 2026. https://datatracker.ietf.org/doc/html/draft-mishra-oauth-agent-grants-02 Pin it. Not a WG item.
Individual draft. Positions itself as a profile, not a rival protocol to AAuth. Cross-domain hops should use identity chaining rather than private formats. Reference implementation 'Grantex' is explicitly non-normative.