Agent Authorization Profile AAP

Overview

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 ^[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 ^[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 ^[4]. The Workload Authorization Grant, the identity-continuation assertion, and the Agent-Delegation header are separate records from both AAP documents.

Discovery and probe

OAuth 2.0 authorization-server metadata plus structured JWT claims; no dedicated well-known file defined in the spec text reviewed

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

Not probed live: no-fixed-path. AAP is a claims profile inside OAuth tokens; nothing at a fixed path proves it.

Instances

• OpenA2A Agent Authorization Protocol (AAP) Authority · Observed 2026-07-02 · trust authority

Every instance with its source is listed on the instances page.

See also

• Builds on: OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization)
• Pairs with: Agent Authorization Grant, OAuth Profile for Delegated AI Agent Authorization, OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization), HTTP Message Signatures, Identity Assertion JWT Authorization Grant (ID-JAG), OpenA2A Agent Authorization Protocol
• Not to be confused with: AAP also collides with the unrelated Automated Access Point / Advanced Authoring Program acronyms in other domains, Agent Attribution Protocol (AAP), OpenA2A Agent Authorization Protocol (draft-fane-opena2a-aap-02), a different current individual draft recorded as opena2a-aap

References

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/ (2026-08-11) VERIFIED
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 (2026-02-07) REPORTED
3. Expired Internet-Draft (expired 2026-08-11) — https://datatracker.ietf.org/doc/draft-aap-oauth-profile/ (2026-02-07) VERIFIED
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 (2026-09-30) VERIFIED

Disputed: This record is the expired individual draft draft-aap-oauth-profile-01. A different document, draft-fane-opena2a-aap-02, is current through 3 April 2027 and is recorded separately as opena2a-aap. The Workload Authorization Grant, the identity-continuation assertion, and the Agent-Delegation header are further separate records.

Verification log and errata

• 2026-10-20 — noted that draft-fane-opena2a-aap-02 is a different, unexpired draft and is recorded as opena2a-aap; this record stays draft-aap-oauth-profile-01
• 2026-10-16 — Expired Internet-Draft (expired 2026-08-11)
• 2026-09-06 — verified against datatracker.ietf.org/doc/draft-aap-oauth-profile/ and github.com/aapspec/spec; found expired