Bind delegated credentials to organization and client identity
A valid credential can be paired with another organization ID in the URL.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Tenant isolation
Estimated field mix
- Security80%
- API design20%
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 operations platform lets customers connect automation clients. Broad API keys and inconsistent tenant checks make delegated access difficult to review.
Setup prerequisites
- Create a local authorization service and synthetic partner clients for two organizations; generate disposable test credentials only.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Store organization and client authority server-side.
- Require exact binding on each service call.
- Reject caller attempts to substitute actor identity.
Implementation constraints
- Opaque credentials are never interpreted as authorization claims without lookup or verification.
Verification to include
- Call an owned resource.
- Reuse the credential against another organization and deny safely.
Deliverables
- Credential authority model.
Rollout and recovery
Fail closed on missing client or membership authority.
Value of the work
For the engineer: Practice delegated authorization, resource scoping, and secure public API ergonomics.
For the team: Provide usable partner access that remains least-privilege and revocable.
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.