Show token last-use status without claiming it proves nonuse
Administrators interpret an empty last-used field as proof that a token was never used, despite audit ingestion gaps.
- Focused work estimate
- 1h 15m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Security UX · Observability
Estimated field mix
- Security70%
- Site reliability30%
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
- ATOKEN-106 · Make revocation override cached authentication results
- ATOKEN-108 · Record denied API access without turning audit logs into a token store
- ATOKEN-107 · Prevent a retry from issuing multiple replacement credentials
- ATOKEN-109 · Rehearse credential exposure containment for one organization
Acceptance criteria
- Distinguish observed use, no recorded use and unknown coverage.
- State the observation window and freshness.
- Avoid exposing request payloads in token summaries.
Implementation constraints
- Treat last-use metadata as operational evidence with stated limits.
Verification to include
- Record a successful request and show its observation time.
- Remove audit coverage and show unknown instead of never used.
Deliverables
- Token activity projection
Rollout and recovery
Publish the explicit coverage labels; revert UI wiring if scope checks fail.
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.