Design the static-to-workload identity cutover
The team must migrate without leaving a forgotten permanent credential active.
- Focused work estimate
- 5h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Migration design · Security tradeoffs
Estimated field mix
- System design40%
- Security40%
- 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.
- 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
- BIDENT-107 · Rotate signing keys with a bounded overlap window
- BIDENT-108 · Revoke one workload without disrupting unrelated exporters
Acceptance criteria
- Inventory callers and staged cutover order.
- Define proof that no caller requires the old credential.
- Compare rollback availability against retained-secret risk.
Implementation constraints
- Do not restore broad credentials automatically on failure.
Verification to include
- Migrate two synthetic callers and revoke the old key.
- Detect a forgotten caller before declaring the migration complete.
Deliverables
- Identity migration decision record.
Rollout and recovery
Use a reviewed emergency path; retire the static key after verified caller migration.
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.