Skip to content

Protocol: use snake_case token names in diagrams for consistency #24

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rohanharikr wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Protocol: use snake_case token names in diagrams for consistency #24

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c111981
Protocol: use agent_token in diagrams for consistency
rohanharikr May 7, 2026
12b715d
Protocol: use auth_token in diagrams for consistency
rohanharikr May 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 16 additions & 16 deletions draft-hardt-oauth-aauth-protocol.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -254,7 +254,7 @@ The agent signs requests with its agent token (#agent-tokens). The resource veri
~~~ ascii-art
Agent Resource
| |
| HTTPSig w/ agent token |
| HTTPSig w/ agent_token |
|-------------------------------------------->|
| |
| 200 OK |
Expand All @@ -269,7 +269,7 @@ The resource handles authorization itself — via interaction (#user-interaction
~~~ ascii-art
Agent Resource
| |
| HTTPSig w/ agent token |
| HTTPSig w/ agent_token |
|-------------------------------------------->|
| |
| 202 (interaction required) |
Expand All @@ -284,7 +284,7 @@ Agent Resource
| AAuth-Access: opaque-token |
|<--------------------------------------------|
| |
| HTTPSig w/ agent token |
| HTTPSig w/ agent_token |
| Authorization: AAuth opaque-token |
|-------------------------------------------->|
| |
Expand All @@ -300,22 +300,22 @@ The resource has no separate access server — it accepts identity claims from w
~~~ ascii-art
Agent Resource PS
| | |
| HTTPSig w/ agent token | |
| HTTPSig w/ agent_token | |
| POST authorization_endpoint | |
|------------------------------------->| |
| | |
| resource_token (aud = PS URL) | |
|<-------------------------------------| |
| | |
| HTTPSig w/ agent token | |
| HTTPSig w/ agent_token | |
| POST token_endpoint | |
| w/ resource_token | |
|-------------------------------------------------->|
| | |
| auth_token | |
|<--------------------------------------------------|
| | |
| HTTPSig w/ auth token | |
| HTTPSig w/ auth_token | |
| GET /api/documents | |
|------------------------------------->| |
| | |
Expand All @@ -331,14 +331,14 @@ The resource has its own access server. The resource issues a resource token (#r
~~~ ascii-art
Agent Resource PS AS
| | | |
| HTTPSig w/ agent token | | |
| HTTPSig w/ agent_token | | |
| POST authorization_endpoint | | |
|------------------------------------>| | |
| | | |
| resource_token (aud = AS URL) | | |
|<------------------------------------| | |
| | | |
| HTTPSig w/ agent token | | |
| HTTPSig w/ agent_token | | |
| POST token_endpoint | | |
| w/ resource_token | | |
|-------------------------------------------->| |
Expand All @@ -354,7 +354,7 @@ Agent Resource PS AS
| auth_token | | |
|<--------------------------------------------| |
| | | |
| HTTPSig w/ auth token | | |
| HTTPSig w/ auth_token | | |
| GET /api/documents | | |
|------------------------------------>| | |
| | | |
Expand Down Expand Up @@ -403,7 +403,7 @@ The agent proposes a mission at the PS. The PS and user may clarify and refine b
~~~ ascii-art
Agent PS User
| | |
| HTTPSig w/ agent token | |
| HTTPSig w/ agent_token | |
| POST mission_endpoint | |
| proposal | |
|--------------------------------------->| |
Expand All @@ -425,7 +425,7 @@ The agent includes the `AAuth-Mission` header when sending requests to resources
~~~ ascii-art
Agent Resource
| |
| HTTPSig w/ agent token |
| HTTPSig w/ agent_token |
| AAuth-Mission: approver=...; s256=... |
| POST authorization_endpoint |
|-------------------------------------------->|
Expand All @@ -443,7 +443,7 @@ When the agent believes the mission is complete, it proposes completion via the
~~~ ascii-art
Agent PS User
| | |
| HTTPSig w/ agent token | |
| HTTPSig w/ agent_token | |
| POST interaction_endpoint | |
| type=completion, summary | |
|--------------------------------------->| |
Expand Down Expand Up @@ -2612,11 +2612,11 @@ See (#call-chaining) for normative requirements. Resource 1 acts as an agent, se
Agent Resource 1 Resource 2 PS
| | | |
| HTTPSig w/ | | |
| auth token | | |
| auth_token | | |
|------------->| | |
| | | |
| | HTTPSig w/ | |
| | R1 agent token | |
| | R1 agent_token | |
| | AAuth-Mission | |
| |--------------->| |
| | | |
Expand All @@ -2637,7 +2637,7 @@ Agent Resource 1 Resource 2 PS
| |<---------------------------------|
| | | |
| | HTTPSig w/ | |
| | auth token | |
| | auth_token | |
| |--------------->| |
| | | |
| | 200 OK | |
Expand Down Expand Up @@ -2699,7 +2699,7 @@ User Agent Resource 1 Resource 2 PS
| | gets auth_token] | |
| | | | |
| | | HTTPSig w/ | |
| | | auth token | |
| | | auth_token | |
| | |-------------->| |
| | | | |
| | | 200 OK | |
Expand Down
Loading