Recheck export authority when a background job completes
An administrator starts a large partner export and loses membership while it runs. The worker later emails a long-lived storage URL using authorization captured only at request time.
- Focused work estimate
- 5h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Asynchronous authorization · Revocation · Artifact access · Time-of-check races
Estimated field mix
- Security60%
- Distributed systems20%
- Storage systems20%
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
- Record immutable request scope without treating it as permanent authorization.
- Reauthorize delivery and each download against current membership and export scope.
- Revoked users cannot receive or use new access grants; completed artifacts remain tenant-restricted.
Implementation constraints
- Use an authenticated download boundary or similarly revocable design; do not send real email in this exercise.
Verification to include
- Complete and download a permitted synthetic export.
- Revoke access between request, completion, and download; verify denial at each relevant boundary.
Deliverables
- Export authorization lifecycle and revocation timing tests
Rollout and recovery
Route synthetic exports through the new download boundary; expire legacy links before removing their compatibility path.
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.