A 51-page draft published on 27 October runs fourteen agent scenarios through OAuth 2.0 and reports where the framework gives out: consent prompts stripped of the intent behind them, delegation chains a resource server cannot verify, and revocation that still has to be done one token at a time.
What happened
On 27 October 2026, Meiling Chen and Jia Chen (China Mobile), Jiankang Yao (CNNIC), Yuning Jiang, Peter Chunchi Liu (Huawei) and Xiang Liu published revision 05 of “Agent Authorization use cases and gap analysis”, draft-chen-oauth-agent-authz-use-cases-05, in the OAuth working group’s document space as an individual submission. It is an Informational Internet-Draft of 51 pages, expires 30 April 2027, and carries the standard notice that it is not endorsed by the IETF and has no formal standing in the standards process.
It does not propose a protocol. It does three things: define the actors in agent authorization, enumerate use cases, and test each against OAuth 2.0 (RFC 6749) and its common extensions.
The use cases are organised in three categories:
- Personal and consumer (7). A personal digital assistant; daily small-amount orders; smart home and automation; the agent as a user’s full proxy to third-party tools; the agent as a proxy to operating-system resources; a first connection to a service with no authorization front channel; a first connection where the front channel exists but the client does not use it.
- Enterprise and business process (6). Complex business-process automation; a coordinated task group; an automated DNSSEC DS-record maintenance agent; managed services; cross-organisational delegation between fully provisioned organisations; an industrial agent for equipment maintenance.
- Security and administration (1). Automated security incident response.
The three structural gaps
Section 3 names the failures that recur across the use cases.
The authorization context gap. A user says “plan my trip” at time T1. Days later the agent requests a booking-API token at time T2, and the consent screen says only: allow this assistant to access your booking service? The intent that made the request sensible never reaches the authorization server, so the user either approves blind or refuses a legitimate request.
The delegation chain gap. When user → agent A → agent B → agent C → bank API is the path, the resource server validates only agent C’s token. It cannot look back up the chain to confirm that C acts for B, B for A, and A under the user’s grant. The draft’s consequence: no end-to-end assurance, auditing that cannot reconstruct authority, and no enforcement of narrowing permissions down the chain.
The mass revocation gap. RFC 7009 revocation is per token. When an account is compromised and many agents hold live tokens, an administrator revokes them one at a time, and the draft is explicit that this sequential window is the vulnerability.
The seven gaps in the summary
Section 6 condenses the analysis into seven findings:
- OAuth’s model is pre-approval; agents need continuous, just-in-time authorization as a task evolves from intent.
- There is no standard interactive channel for an agent to pause and ask the user for an intermediate decision, or to answer a real-time challenge from a resource server.
- Standard tokens cannot represent a multi-step delegation chain — called a critical blocker for multi-agent business processes.
- Revocation is inadequate: no standard APIs for task-level or bulk (per-user, per-client) revocation.
- Authorization is modelled per client, not per group: no representation of a set of clients acting as one task group under one grant, no admission of late-selected members, no group-level lifecycle or atomic revocation.
- A grant-layer versus execution-layer gap: OAuth expresses what an agent is allowed to do, but not non-repudiable evidence of consent for a specific high-risk action at the moment it happens — the draft’s phrasing is that grant-layer tokens “prove potential, not the legitimacy of a specific, executed transaction”.
- No machine-readable terminal disposition when a client receives an authorization challenge and fails or declines it, leaving the resource server to infer state from silence.
Section 5 checks the obvious candidates — Rich Authorization Requests (RFC 9396), DPoP (RFC 9449), the Client ID Metadata Document draft, and transaction tokens — and finds none of them closes the delegation-chain gap on its own. The security considerations add the familiar failure modes: broad long-lived “god tokens” standing in for dynamic authorization, confused-deputy attacks in custom delegation code, revocation timeliness, non-repudiation, and a coordinator agent that becomes a single point of authority for a whole task group if it is compromised.
Why it matters for KYA
This is a usable requirements list, and it is written by people building the flows rather than selling a control plane. The seven gaps map almost one-to-one onto the questions a KYA review asks: who authorised this action, can you prove the chain from principal to acting agent, can you show consent for this specific transaction, and can you cut everything off at once when the answer is wrong.
The grant-layer/execution-layer distinction is the KYA argument in OAuth’s own vocabulary. A token proves an agent was permitted to act, not that a particular action was authorised at the moment it happened. Anyone assembling an audit trail for an agent should be able to say which of the two they are storing, because most incident reviews need the second and most systems only have the first.
Revocation is where agent identity claims get tested. A registry entry and a signed credential are only as good as the speed at which they can be withdrawn. The draft’s point that bulk revocation is missing from the framework is the practical version of a claim agent-identity vendors make loosely: the standard revocation primitive is one token at a time, and everything faster is a vendor’s own mechanism.
It also shows the standards work is still pre-normative. Three of the gaps — continuous authorization, group authority, execution-layer consent evidence — are each being attacked by separate individual drafts, with no adopted work item tying them together. Until that changes, every agent-authorization deployment is an integration project with its own answer to “what is a delegation chain”.
Caveats
An individual Internet-Draft, not a working-group document: no IETF consensus, no adoption, and it will expire in April 2027 unless it is revised. Its authors are from two carriers, a registry and a vendor, which shapes the use-case selection; there is no proposed wire format to evaluate. The value here is the gap list and the vocabulary, not a solution. The draft was published the day after the OAuth working group’s interim meeting of 26 October 2026; this article does not infer from the timing that the document reflects working-group conclusions.
Sources
- M. Chen, J. Chen, J. Yao, Y. Jiang, C. P. Liu, X. Liu, “Agent Authorization use cases and gap analysis”,
draft-chen-oauth-agent-authz-use-cases-05, IETF Internet-Draft, 27 October 2026 — datatracker.ietf.org. - Full text — ietf.org.
- OAuth working group interim meeting, 26 October 2026, materials — datatracker.ietf.org.
- D. Hardt, “The OAuth 2.0 Authorization Framework”, RFC 6749 — rfc-editor.org.
- J. Richer (ed.), “OAuth 2.0 Token Revocation”, RFC 7009 — rfc-editor.org.
Know Your Agent (KYA) explains agent identity, verification and accountability. This is an explainer, not legal or compliance advice — see our Sources & methodology. New to KYA? Start with What is Know Your Agent? and the glossary.