Rotate signing keys with a bounded overlap window
Immediate key replacement breaks in-flight exports while indefinite overlap preserves old authority.
- Focused work estimate
- 3h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Key lifecycle
Estimated field mix
- Security60%
- Cloud infrastructure40%
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 export worker shares a long-lived object-store credential across environments. The team needs a provider-neutral identity boundary with safe expiry and revocation.
Setup prerequisites
- Create a local identity issuer and object-store double using generated test-only keys; no cloud account or production secret.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- BIDENT-101 · Inventory the export worker's required storage operations
- BIDENT-102 · Bind workload assertions to issuer, audience, and environment
- BIDENT-103 · Issue short-lived storage grants with exact resource scope
- BIDENT-104 · Refresh credentials before expiry without creating a refresh storm
- BIDENT-105 · Keep clock skew from extending grant lifetime indefinitely
- BIDENT-106 · Prevent identity-provider outages from selecting static credentials
Acceptance criteria
- Publish new verification key before issuance switches.
- Bound old-key acceptance by policy and token expiry.
- Reject retired keys after the overlap.
Implementation constraints
- Private keys remain test-only runtime inputs.
Verification to include
- Complete an in-flight old-key export during overlap.
- Reject an old-key token after retirement.
Deliverables
- Key rotation rehearsal.
Rollout and recovery
Retain the previous public verifier only for the declared overlap.
Value of the work
For the engineer: Practice workload identity, audience restrictions, and credential lifecycle failures.
For the team: Produce a migration path that narrows credential scope and makes revocation observable.
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.