Task library BIDENT
Project scope 10 tickets / 3 phases
Total focused work estimate 27h + setup
Suggested stack TypeScript · JWT · HTTP Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.
Choose a bounded subset for an assessment or practice session. Prerequisites and remaining project work must be agreed separately.
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Pattern topics identify design choices to practice. Read the ticket's acceptance criteria and justify the simplest suitable approach. Tags are not capability or ownership evidence; an untagged ticket has no curated pattern topic assigned.
Recommended next step Start with BIDENT-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice workload identity, audience restrictions, and credential lifecycle failures.
What the team gains Produce a migration path that narrows credential scope and makes revocation observable.
Before you start Create a local identity issuer and object-store double using generated test-only keys; no cloud account or production secret. Delivery agreement Deliver local identity contracts and rotation rehearsals; deploy no live trust policy.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Bind identities to workloads and resources.
PHASE 2 Validate tokens, caching, and provider failures.
PHASE 3 Test rotation, revocation, and migration recovery.
Define trust scope Bind identities to workloads and resources.
BIDENT-101 Entry ticket; project setup still required Estimated field mix
Security 80% Cloud infrastructure 20% BIDENT-102 Depends on BIDENT-101 Estimated field mix
Security 80% Cloud infrastructure 20% Issue bounded credentials Validate tokens, caching, and provider failures.
BIDENT-103 Depends on BIDENT-102 Estimated field mix
Security 70% Cloud infrastructure 30% BIDENT-104 Depends on BIDENT-103 Estimated field mix
Performance engineering 50% Security 30% Cloud infrastructure 20% BIDENT-105 Depends on BIDENT-102, BIDENT-104 Estimated field mix
Security 80% Cloud infrastructure 20% BIDENT-106 Depends on BIDENT-104, BIDENT-105 Estimated field mix
Security 50% Site reliability 30% Cloud infrastructure 20% Rehearse lifecycle changes Test rotation, revocation, and migration recovery.
BIDENT-107 Depends on BIDENT-105, BIDENT-106 Estimated field mix
Security 60% Cloud infrastructure 40% BIDENT-108 Depends on BIDENT-107 Estimated field mix
Security 80% Cloud infrastructure 20% BIDENT-109 Depends on BIDENT-106, BIDENT-108 Estimated field mix
System design 40% Security 40% Cloud infrastructure 20% BIDENT-110 Depends on BIDENT-109 Estimated field mix
Security 50% Site reliability 50% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.