Credentials, revocation and retries

Credentials, revocation and retries

A failed request does not prove that the company did nothing. Retrying the same business operation also does not mean reusing every authentication field.

Keep token roles separate

A Session Token provides short-lived access. An Account Token is a long-lived OAuth refresh token used to obtain signed-in Session Tokens. Send the Account Token only to the appropriate token endpoint. Keep it out of model context, conversations, URLs and logs.

Implement key binding and DPoP according to the specification. Knowing a token string alone does not establish legitimate use. Signing out, disconnecting a personal agent and ending a session have different effects.

Same operation, fresh proof

The official guides recommend reusing the business Idempotency-Key when retrying a write API that supports it. Create a new DPoP proof for each retry and a new assertion for a retried token request. An already-seen jti can be rejected as a replay. Business identifiers and authentication proofs solve different problems.

Respect Retry-After on 429 responses. Use bounded exponential backoff with jitter for other retryable failures. Do not retry authorization failures indefinitely or present a timeout as proof of non-execution.

Logging

Redact Authorization, DPoP, Cookie and credential fields before requests enter logs and tracing. Record the stage, error category and non-secret correlation data. Avoid copying full requests into a model for troubleshooting.

Sources: draft 0.2 and official guides, checked 2026-11-16.

Last updated on