Design migration from broad keys to scoped delegated clients
Existing integrations depend on broad keys and cannot all migrate at once.
- Focused work estimate
- 5h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- API strategy · Security tradeoffs
Estimated field mix
- Security50%
- System design30%
- 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.
- BAPIAUTH-101 · Define partner scopes from concrete API operations
- BAPIAUTH-102 · Bind delegated credentials to organization and client identity
- BAPIAUTH-103 · Return non-enumerating errors for unauthorized partner resources
- BAPIAUTH-104 · Enforce authorization in nested and batch partner operations
- BAPIAUTH-105 · Rotate partner credentials without indefinite dual-key access
- BAPIAUTH-106 · Revoke partner access across cached authorization decisions
- BAPIAUTH-107 · Rate-limit by delegated client without losing tenant-wide protection
- BAPIAUTH-108 · Expose an audit trail of privileged partner-client changes
Acceptance criteria
- Inventory actual required operations through safe synthetic usage records.
- Define staged scope reduction and client cutover.
- Compare compatibility burden with the risk of retained broad authority.
Implementation constraints
- No real partner usage is inferred from absence of traffic.
Verification to include
- Migrate two synthetic clients with different needs.
- Keep an unknown integration unresolved instead of silently revoking or broadening it.
Deliverables
- Delegated-access migration plan.
Rollout and recovery
Use explicit reviewed deadlines and retain a bounded recovery process.
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.