Return non-enumerating errors for unauthorized partner resources
Partners can distinguish nonexistent records from records belonging to another organization.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Error design · Privacy
Estimated field mix
- API design40%
- Security40%
- Privacy engineering20%
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
- Define stable safe denial semantics.
- Keep error bodies free of foreign identifiers.
- Preserve internal diagnostic categories separately.
Implementation constraints
- Use Problem Details-style public errors.
Verification to include
- Read an authorized record.
- Compare missing and foreign-record public responses.
Deliverables
- Partner error contract.
Rollout and recovery
Use the same safe projection across all resource endpoints.
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.