Narrow integration keys to the permissions they were issued
A partner creates a read-only reporting key while an administrator is logged in. Requests using that key inherit the administrator's full session permissions.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- API key scopes · Least privilege · Credential revocation
Estimated field mix
- Security80%
- Backend20%
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 manufacturing company shares purchase-order documents with partner organizations. Buyers, partner administrators, and read-only agents use the same API. Recent support reports suggest list filters and background downloads disagree about who may see an order.
Setup prerequisites
- HTTP APIs
- Session authentication
- Tenant-scoped data access
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Evaluate key scopes separately from browser-session roles.
- Restrict effective permissions to both key scope and current partner authority.
- Support key revocation without disabling unrelated partner sessions.
Implementation constraints
- A key cannot grant a permission its issuer was not authorized to delegate.
Verification to include
- Read permitted reports through a scoped synthetic key.
- Attempt order edits, cross-partner reads, and use after revocation; assert denial.
Deliverables
- Integration-key authorization policy and scope tests
Rollout and recovery
Create scoped test keys alongside existing clients; remove broad key support after explicit client migration.
Value of the work
For the engineer: Practice authorization as a service-level invariant, including revocation timing, concurrent membership changes, and asynchronous data delivery.
For the team: Inspect a concrete record of cross-organization denial, least-privilege decisions, and access-recovery behavior using fictional partner records.
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.