ITHC: enforce administrative case deletion authorization
This commit is contained in:
@@ -95,20 +95,30 @@ the administrative session and requires a trusted same-origin request. It also
|
||||
validates the requested container, case-folder segment, and representation-file
|
||||
segment before performing deletion.
|
||||
|
||||
Administrative cross-container case deletion uses the dedicated
|
||||
`POST /api/admin/deleteblobcase` route. That endpoint independently validates
|
||||
the administrative session, requires a trusted same-origin request, and
|
||||
validates the requested container and case-folder segment before performing
|
||||
deletion. It invokes the same existing `deleteBlobCase(container,
|
||||
casefolderID)` operation as the ordinary endpoint. That operation lists and
|
||||
deletes blobs in the selected container whose names begin with the supplied
|
||||
case-folder prefix; it does not delete the Azure container or broaden deletion
|
||||
to unrelated containers.
|
||||
|
||||
Administrative representation JSON unlocking uses the dedicated
|
||||
`POST /api/admin/editRepJson` route. That endpoint independently validates the
|
||||
administrative session, requires a trusted same-origin request, and validates
|
||||
the requested container and blob path before removing `repComplete`. The former
|
||||
`/api/file/editRepJson` route is retired and no longer performs storage access.
|
||||
|
||||
Administrative case deletion was not investigated or remediated as part of
|
||||
Stage 3 and remains a separate, unverified security boundary. The other
|
||||
administrative API and storage limitations documented above also remain open.
|
||||
|
||||
Automated contract verification for the implemented deletion controls has
|
||||
passed. Live Azure behaviour, browser-level behaviour, and deployment
|
||||
configuration have not been verified by that automated coverage. These changes
|
||||
do not establish closure of the overall ITHC finding.
|
||||
passed, including ordinary ownership/HMAC rejection, administrative method,
|
||||
session, origin and input rejection, zero deletion calls on rejected requests,
|
||||
and exact cross-container helper arguments on success. Live Azure behaviour,
|
||||
browser-level behaviour, and deployment configuration have not been verified
|
||||
by that automated coverage. The other administrative API and storage
|
||||
limitations documented above remain open, and these changes do not establish
|
||||
closure of the overall ITHC finding.
|
||||
|
||||
## Deployment requirements before production use
|
||||
|
||||
|
||||
Reference in New Issue
Block a user