TASK22028: expand signer coverage for delete flows
This commit is contained in:
@@ -1045,3 +1045,40 @@ Validation:
|
||||
Follow-ups:
|
||||
|
||||
- Keep signer allow-list additions minimal and path-specific.
|
||||
|
||||
---
|
||||
|
||||
### CL-029: Follow-up fix — signer coverage for additional delete flows
|
||||
|
||||
date: 2026-03-13
|
||||
author: Cline
|
||||
scope: `actions/services/{portalDirectService,documentDirectService}.js`, `pages/api/endpoint/gethash_api.js`, `tests/phase7/service-behaviour.test.cjs`, `tests/phase14/service-behaviour.test.cjs`
|
||||
type: change
|
||||
rationale: Resolve browser hash-signing gaps for additional delete operations still using direct client hash generation.
|
||||
impact: Restores browser-safe signing for delete watched cases, delete my representations, and delete blob representation/awaiting-submission paths while retaining authenticated allow-list signer model.
|
||||
status: completed
|
||||
|
||||
Summary:
|
||||
|
||||
- Updated signer allow-list to include:
|
||||
- `/api/endpoint/deletemyrepresentations_api`
|
||||
- `/api/endpoint/deletewatchedcases_api`
|
||||
- `/api/file/deleteblobrep`
|
||||
- Migrated direct service calls to signer-based hash retrieval for:
|
||||
- `portalDirectService.deleteWatchedCases`
|
||||
- `portalDirectService.deleteMyRepresentations`
|
||||
- `documentDirectService.deleteAwaitingSubmissionsFromBlob`
|
||||
- `documentDirectService.deleteMyRepresentationsFromBlob`
|
||||
- Extended focused tests:
|
||||
- `tests/phase7/service-behaviour.test.cjs` (service signer usage)
|
||||
- `tests/phase14/service-behaviour.test.cjs` (allow-list coverage)
|
||||
|
||||
Validation:
|
||||
|
||||
- `node tests/phase7/service-behaviour.test.cjs` -> pass (12/12)
|
||||
- `node tests/phase14/service-behaviour.test.cjs` -> pass (9/9)
|
||||
- `npm run lint` -> warnings only (pre-existing)
|
||||
|
||||
Follow-ups:
|
||||
|
||||
- Keep allow-list expansion path-scoped and driven by concrete browser-call requirements only.
|
||||
|
||||
Reference in New Issue
Block a user