Make revocation override cached authentication results
An administrator revokes a leaked token, but one process continues accepting its cached authority.
- Focused work estimate
- 5h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Cache consistency · Revocation
Estimated field mix
- Security60%
- Distributed systems40%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional B2B export API uses long-lived tokens. Tokens copied between organizations can access too much, and revocation takes effect unpredictably.
Setup prerequisites
- Create a local synthetic API and two isolated organizations.
- Use generated disposable credentials only.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- ATOKEN-101 · Define token scopes as an explicit allowlist of export operations
- ATOKEN-102 · Store only token verification material and a safe display prefix
- ATOKEN-103 · Bind API token queries to the issuing organization
- ATOKEN-104 · Enforce token expiration at the request authorization boundary
- ATOKEN-105 · Rotate a token with a bounded overlap window
Acceptance criteria
- Define a maximum revocation propagation contract.
- Invalidate or version cached authority using durable token state.
- Fail closed when required revocation freshness cannot be established.
Implementation constraints
- Use two local consumer instances and controlled connectivity failures.
Verification to include
- Revoke a token and verify both consumers deny within the declared bound.
- Disconnect revocation freshness and verify the documented denial behavior.
Deliverables
- Revocation protocol and propagation probe
Rollout and recovery
Canary two synthetic consumers; reduce cache lifetime or disable caching on propagation failure.
Value of the work
For the engineer: Practice authorization boundaries, credential lifecycle and safe diagnostics.
For the team: Review denial paths and operational control over service access.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.