Agent Authorization use cases and gap analysis#

Meiling Chen (China Mobile).

• Why: The requirements document that justifies (and scopes) the OAuth WG's agent work — read it to understand why AIMS, PEDIGREE and delegate SD-JWT all exist.
• What: Ten use cases across consumer, enterprise and security scenarios, each with authorization requirements and gaps: intent-to-permission mapping and interactive consent loops for personal assistants; scope explosion and missing conditional context in smart homes; the confused-deputy/agent-flagging problem when agents hit human-facing services (the "agent downloads 400 papers and gets the user's account banned" example); multi-hop delegation chains and group authorization for agent teams; and global/bulk revocation gaps (RFC 7009 revokes one token at a time — useless in an incident).
• How: Gap analysis against RAR (too static), DPoP (fixed keys break agent migration), Transaction Tokens (internal-only), and CIMD (no agent metadata, no delegation traceability), each with proposed optimizations like attenuating agent tokens and parent_agent_id claims.
• Where applicable: Vendor-neutral; informational individual draft -01 with biweekly open meetings — the input document for whatever OAuth extensions follow.