Keep clock skew from extending grant lifetime indefinitely
A large token leeway makes expired credentials valid far longer than intended.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Time validation
Estimated field mix
- Security80%
- 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
- Bound allowed skew explicitly.
- Reject impossible issue and expiry ordering.
- Report clock-related failures without token contents.
Implementation constraints
- Use an injected clock for deterministic checks.
Verification to include
- Accept a token inside the declared skew window.
- Reject expired and future-issued tokens beyond the bound.
Deliverables
- Expiry boundary tests.
Rollout and recovery
Deploy with monitored clock assumptions; stop issuance if time authority is unavailable.
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.