Define token scopes as an explicit allowlist of export operations
A token marked read-only can still trigger an export job because the handler treats every authenticated token equally.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Authorization · Least privilege
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 B2B export API uses long-lived tokens. Tokens copied between organizations can access too much, and revocation takes effect unpredictably.
Setup prerequisites
- Create a local synthetic API and two isolated organizations.
- Use generated disposable credentials only.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- List exact read and create operations per scope.
- Unknown scopes are rejected at issuance.
- Protected handlers deny missing required scope.
Implementation constraints
- Do not infer permission from token naming conventions.
Verification to include
- Use a read scope for a permitted status request.
- Attempt export creation with that token and verify no job is created.
Deliverables
- Scope matrix and authorization checks
Rollout and recovery
Deploy handler checks before issuing scoped tokens; disable legacy unrestricted issuance.
Value of the work
For the engineer: Practice authorization boundaries, credential lifecycle and safe diagnostics.
For the team: Review denial paths and operational control over service access.
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.