Refresh credentials before expiry without creating a refresh storm
Every concurrent request refreshes the same expiring credential.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Caching · Concurrency
Estimated field mix
- Performance engineering50%
- Security30%
- Cloud infrastructure20%
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.
Acceptance criteria
- Coalesce equivalent in-flight refreshes.
- Refresh within a declared bounded window.
- Avoid caching failed or mismatched grants.
Implementation constraints
- Cache keys include workload, resource scope, and audience.
Verification to include
- Share one refresh across concurrent requests.
- Reject cross-scope cache reuse and retry a failed refresh safely.
Deliverables
- Credential cache.
Rollout and recovery
Use short cache lifetimes; clear affected entries on validation failure.
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.