Verify the current member before accepting profile removal
A request body supplies a profile ID and the API trusts it even when it differs from the authenticated member.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Authorization · Session validation
Estimated field mix
- Security70%
- Privacy engineering30%
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 collaboration product lets a member request removal of their personal profile. Search, notifications and cached displays retain copies after the primary row disappears. The exercise uses a documented product deletion policy and synthetic identities.
Setup prerequisites
- Create local profile, search-index and notification fixtures with controlled provider failures.
- Define synthetic members, organizations and a current-session authorization fixture.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Resolve the subject from the current authorized session and declared command scope.
- Reject substituted profile IDs and stale sessions before creating a request.
- Return a safe request reference without exposing another profile’s existence.
Implementation constraints
- Reuse an explicit authentication provider fixture; this ticket does not invent a new identity-assurance claim.
Verification to include
- Submit as the matching synthetic member and verify the request subject.
- Substitute a second member’s ID and revoke the session; both cases must create no request.
Deliverables
- Authorized request endpoint and subject-substitution tests
Rollout and recovery
Gate request creation before enabling background work; rollback disables new requests while preserving accepted ones.
Value of the work
For the engineer: Practice distributed cleanup, identity scope, idempotency and accurate user-facing lifecycle states.
For the team: Produce a reviewable deletion workflow and copy inventory for adaptation to an approved company policy.
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.