--- type: Agentic Web Standard title: "Agent Authorization Profile" description: "How can OAuth 2.0/JWT claims carry structured agent identity, task context, operational constraints, delegation chains, and human-oversight requirements for machine-to-machine agent calls?" resource: "https://www.ietf.org/archive/id/draft-aap-oauth-profile-01.html" tags: ["permit", "endpoint", "community", "delegate-user-authority", "prove-agent-identity", "audit-agent-actions"] status: deprecated generated: { by: agenticweb-builder/1.0, at: 2026-10-30T00:00:00Z } verified: { by: process:agenticweb-engine, at: 2026-10-23T00:00:00Z } stale_after: 2026-11-22T00:00:00Z sources: - id: ref-1 resource: "https://datatracker.ietf.org/doc/draft-aap-oauth-profile/" title: "The IETF Datatracker's document page for draft-aap-oauth-profile shows Document Type 'Expired Internet-Draft (individual)', IESG state 'Expired', last updated 2026-08-11, author 'angel cruz' with a note that the author's listed e-mail may no longer be valid." last_modified: 2026-08-11T00:00:00Z - id: ref-2 resource: "https://github.com/aapspec/spec" title: "The aapspec/spec GitHub repository hosts the same spec under an Apache 2.0 license, links a separate reference-impl repository, and its own README's IETF-status checklist shows no item beyond draft submission checked off, with zero GitHub stars and no commits after the 2026-02-07 draft date." last_modified: 2026-02-07T00:00:00Z - id: ref-3 resource: "https://datatracker.ietf.org/doc/draft-aap-oauth-profile/" title: "Expired Internet-Draft (expired 2026-08-11)" last_modified: 2026-02-07T00:00:00Z - id: ref-4 resource: "https://www.ietf.org/archive/id/draft-fane-opena2a-aap-02.txt" title: "draft-fane-opena2a-aap-02 (posted 2 October 2026, expires 5 April 2027) is a different Internet-Draft from draft-aap-oauth-profile-01. It is a Standards Track individual submission by A. Fane, OpenA2A, and it was not expired on 2026-10-20." last_modified: 2026-09-30T00:00:00Z --- # Agent Authorization Profile Agent Authorization Profile (AAP) is an agentic-web standard (endpoint) at step 3, Permit, without a single governing body; its status is "Expired Internet-Draft". It answers: "How can OAuth 2.0/JWT claims carry structured agent identity, task context, operational constraints, delegation chains, and human-oversight requirements for machine-to-machine agent calls?" Replacing or extending OAuth profile / scoped service-account token, implementation status is prototype, last verified 2026-10-23. # Overview The Agent Authorization Profile (AAP) is a single-author IETF individual Internet-Draft, draft-aap-oauth-profile-01, dated 2026-02-07, proposing structured OAuth 2.0/JWT claims for autonomous AI agents [^ref-1]. It extends OAuth 2.0, JWT, RFC 8693 Token Exchange, and proof-of-possession mechanisms so that a resource server can reason about agent identity, task context, operational constraints, delegation chains, and whether human oversight is required for a given call, explicitly without introducing a new protocol [^ref-1]. It does not define a discovery mechanism beyond standard OAuth authorization-server metadata, and it does not define content-use or crawling permissions — like DAAP and AAuth, its scope is agent-to-API (M2M) authorization, not publisher content policy. Its distinguishing claim relative to those two overlapping drafts is a heavier emphasis on structured, machine-reasoned claims (delegation chains, human-oversight flags) rather than a minimal composition of existing mechanisms. As of this verification (2026-09-06), the IETF Datatracker's own document-state field shows this draft as an 'Expired Internet-Draft (individual)', IESG state Expired, last updated 2026-08-11 with its single revision (-01) dated 2026-02-07 and no working-group affiliation — it never progressed beyond an individual submission [^ref-1]. The author's listed contact is separately flagged by the Datatracker as possibly no longer valid. A companion project exists at github.com/aapspec, including a spec repository (Apache 2.0 licensed), a claimed reference implementation, JSON Schemas, and test vectors, but the repository's own README shows an IETF-status checklist with no box beyond 'draft-00 submitted' checked, no GitHub stars, and no activity beyond the initial 2026-02-07 push found [^ref-2]. On that basis this record's phase is set to withdrawn and implementation to prototype (a reference implementation is claimed to exist, but with no evidence of independent use). What is unresolved: whether 'angel cruz' or another contributor intends to resubmit an active revision; whether any of AAP's specific claim names have been adopted informally by agent-framework builders outside the IETF process; and how AAP's more prescriptive claim-schema approach compares in practice to the lighter-weight DAAP profile, which explicitly avoids new claims. Given three overlapping, none-adopted individual OAuth-for-agents drafts (AAuth, DAAP, AAP) exist, it remains open which, if any, the OAuth Working Group formally adopts. This expired draft is not the OpenA2A Agent Authorization Protocol. draft-fane-opena2a-aap-02, by A. Fane (OpenA2A), was posted on 2 October 2026 and expires 5 April 2027. It is a Standards Track individual submission, not a working-group document, and it is recorded separately as `opena2a-aap` [^ref-4]. The Workload Authorization Grant, the identity-continuation assertion, and the Agent-Delegation header are separate records from both AAP documents. # Examples ```http GET {authorization_server}/.well-known/oauth-authorization-server # parse: Decode a returned access token as a JWT and check for AAP-specific claim names (agent identity, task binding, delegation chain) as documented in the aapspec/spec repository's JSON Schemas # on absent: No AAP claims present; given the draft's expired status this is the expected default across the ecosystem ``` # Knowledge Graph * **Lifecycle Step**: [3 Permit](/category/permit/index.md) * **Builds on**: [OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization)](/okf/protocols/oauth-metadata-for-agents.md) * **Pairs with**: [Agent Authorization Grant](/okf/protocols/aauth.md), [OAuth Profile for Delegated AI Agent Authorization](/okf/protocols/daap.md), [OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization)](/okf/protocols/oauth-metadata-for-agents.md), [HTTP Message Signatures](/okf/protocols/http-message-signatures.md), [Identity Assertion JWT Authorization Grant (ID-JAG)](/okf/protocols/identity-assertion-authz-grant.md), [OpenA2A Agent Authorization Protocol](/okf/protocols/opena2a-aap.md) [^ref-1]: The IETF Datatracker's document page for draft-aap-oauth-profile shows Document Type 'Expired Internet-Draft (individual)', IESG state 'Expired', last updated 2026-08-11, author 'angel cruz' with a note that the author's listed e-mail may no longer be valid. (https://datatracker.ietf.org/doc/draft-aap-oauth-profile/) [^ref-2]: The aapspec/spec GitHub repository hosts the same spec under an Apache 2.0 license, links a separate reference-impl repository, and its own README's IETF-status checklist shows no item beyond draft submission checked off, with zero GitHub stars and no commits after the 2026-02-07 draft date. (https://github.com/aapspec/spec) [^ref-3]: Expired Internet-Draft (expired 2026-08-11) (https://datatracker.ietf.org/doc/draft-aap-oauth-profile/) [^ref-4]: draft-fane-opena2a-aap-02 (posted 2 October 2026, expires 5 April 2027) is a different Internet-Draft from draft-aap-oauth-profile-01. It is a Standards Track individual submission by A. Fane, OpenA2A, and it was not expired on 2026-10-20. (https://www.ietf.org/archive/id/draft-fane-opena2a-aap-02.txt)