advancedPhase 8

Clarification Chat During Consent

During consent the person asks the agent a question about its stated justification. The PS delivers the question to the agent with 202 and requirement=clarification, the agent answers on the pending URL, and the person sees the answer as part of the consent context. The same requirement is used by an AS asking the PS.

§ Clarification Chat

GET https://api.example/data401

The agent already holds a person token for this resource (see Person Identity Access) and presents it via Signature-Key.

AAuth-Capabilities: clarification tells the resource — and through the resource token, everyone downstream — that this agent can answer questions.

The resource has verified a person token, so it may issue a resource token. It challenges with requirement=auth-token.

1 / 6

speed

Step 1: Signed GET /data with the person token → 401 + resource token

Request / response

Clarification & Consent Timeline

→

GEThttps://api.example/data

Host

api.example

Signature-KeyAAuth?

sig=jwt;jwt="eyJhbGciOiJFZERTQSIsImtpZCI6InBzLWtleS0xIiwidHlwIjoiYWEtcGVyc29uK2p…

Signature-InputAAuth?

sig=("@method" "@authority" "@path" "signature-key");created=1700000000;alg="ed2…

SignatureAAuth?

sig=:U2lnbmF0dXJlQnl0ZXNFeGFtcGxlVmFsdWVGb3JEZW1vbnN0cmF0aW9uUHVycG9zZXNPbmx5:

AAuth-CapabilitiesAAuth?

clarification, interaction

HTTP Signaturescheme=jwt

Covered Components

@method

@authority

@path

signature-key

Signature Base

"@method": GET

"@authority": api.example

"@path": /data

"signature-key": sig=jwt;jwt="eyJhbGciOiJFZERTQSIsImtpZCI6InBzLWtleS0xIiwidHlwIjoiYWEtcGVyc29uK2p3dCJ9…"

"@signature-params": ("@method" "@authority" "@path" "signature-key");created=1700000000;alg="ed25519"

Signature-Key Header

sig=jwt;jwt="eyJhbGciOiJFZERTQSIsImtpZCI6InBzLWtleS0xIiwidHlwIjoiYWEtcGVyc29uK2p3dCJ9…"

Signature-Input Header

sig=("@method" "@authority" "@path" "signature-key");created=1700000000;alg="ed25519"

Person Tokenaa-person+jwt

Header

{"alg":"EdDSA",
"kid":"ps-key-1",
"typ"?Token type identifier. aa-agent+jwt = Agent Token, aa-person+jwt = Person Token, aa-resource+jwt = Resource Token, aa-auth+jwt = Auth Token:"aa-person+jwt"
}

Payload

{"iss"?Issuer — who created and signed this token:"https://ps.example",
"dwk"?Discovery Well-Known — the metadata document name for key discovery (e.g. aauth-agent.json, aauth-person.json):"aauth-person.json",
"aud"?Audience — which party should accept this token:"https://api.example",
"sub"?Subject. In an agent token, the agent identifier. In a person, resource or auth token, the person's directed identifier — opaque, unique within the issuer. Identity is the pair (iss, sub); a sub from one issuer MUST NOT be matched against a record established under another.:"8f14e45fceea167a5a36dedd4bea2543",
"cnf"?Confirmation — proof-of-possession claim binding this token to a key:{"jwk"?JSON Web Key — the public key bound to this token:
},
"jti"?JWT ID — unique identifier for this token (replay detection, audit, revocation):"pt-32d653",
"iat"?Issued At — Unix timestamp when the token was created:1776222894,
"exp"?Expiration — Unix timestamp after which the token is invalid:1776226494
}

sig: cGVyc29uVG9rZW5TaWduYXR1cmVJc3N1…

Resource Tokenaa-resource+jwt

Header

{"alg":"EdDSA",
"kid":"as-key-1",
"typ"?Token type identifier. aa-agent+jwt = Agent Token, aa-person+jwt = Person Token, aa-resource+jwt = Resource Token, aa-auth+jwt = Auth Token:"aa-resource+jwt"
}

Payload

{"iss"?Issuer — who created and signed this token:"https://api.example",
"dwk"?Discovery Well-Known — the metadata document name for key discovery (e.g. aauth-agent.json, aauth-person.json):"aauth-resource.json",
"aud"?Audience — which party should accept this token:"https://as.example",
"jti"?JWT ID — unique identifier for this token (replay detection, audit, revocation):"d07a759e-21ff-4ba5-8dde-7f4917be8741",
"ps"?The person's Person Server. In a resource token, the iss of the person token the resource verified. In an auth token, the PS the person is represented by — and where an intermediary routes a downstream request.:"https://ps.example",
"sub"?Subject. In an agent token, the agent identifier. In a person, resource or auth token, the person's directed identifier — opaque, unique within the issuer. Identity is the pair (iss, sub); a sub from one issuer MUST NOT be matched against a record established under another.:"8f14e45fceea167a5a36dedd4bea2543",
"person_token_jti"?The jti of the person token this resource token was issued against. The PS resolves that exact token and rejects any mismatch, which is what makes mission stripping detectable.:"pt-32d653",
"agent_jkt"?JWK Thumbprint of the agent's signing key. With cnf, this is the only binding to the agent — no token a resource reads carries an agent identifier.:"5j5WMuITu8-cV1RdClUeNgnSg3aLJpCYiFvzcwDgYhI",
"scope"?Authorized scope/permissions granted by this token:"read",
"iat"?Issued At — Unix timestamp when the token was created:1776222894,
"exp"?Expiration — Unix timestamp after which the token is invalid:1776223494
}

sig: ouuGVYcy_PGnxVaY70RR_QM5bT8et2UV…