Rotate a token with a bounded overlap window
Customers need to replace credentials without downtime, but unrestricted overlap leaves old tokens valid indefinitely.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Credential rotation · State transitions
Estimated field mix
- Security80%
- API design20%
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.
Acceptance criteria
- Create a replacement with no broader scopes.
- Persist an explicit predecessor retirement deadline.
- Expose both token identities and overlap state safely.
Implementation constraints
- Require authorized rotation and bind it to an expected token revision.
Verification to include
- Rotate and authenticate both during the declared overlap.
- Advance beyond the overlap and deny the predecessor while accepting the replacement.
Deliverables
- Rotation command and overlap tests
Rollout and recovery
Test with a synthetic client; revoke the new token if adoption fails within the window.
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.