10 lines
1.4 KiB
Markdown
10 lines
1.4 KiB
Markdown
# Admin Audit isolation on the A3 integration branch
|
|
|
|
Applied the controller and regression-test changes from security checkpoint `d4c486681ad51424bfd33545d518e87193ffbc56` to A3 base `2717c6afaf6375e2e1abd7d63cbfa613a802ce83`. Git comparisons confirmed both input files matched the security patch's parent and both outputs matched its committed files. No other security branch changes were integrated.
|
|
|
|
Admin Audit now omits the mailbox subject from imported `ReplyReceived` notes. The loopback HTTP fixture verified anonymous and non-admin denial, the redacted admin response, retained non-private audit details and the unchanged stored owner note. It also verified owner-scoped notification reads and writes and processing detail access. There was no migration or data rewrite.
|
|
|
|
**PASSED 57 selected backend tests**, zero failures or skips, pinned .NET SDK 9.0.317 in Release with no restore. The native [TRX](evidence/admin-audit-isolation/INTEGRATED.trx) records 31 AdminProcessing, 19 Gmail and 7 Users cases. The seven Users cases overlap the separate read-only 2FA checkpoint. The native hash before Git text normalisation is `840180a639bbc63f9869ae013faae33f10507a0152524c89590f44357fcacea5`.
|
|
|
|
The fixtures used an isolated local database and synthetic users. Broader audit minimisation, real MariaDB and live provider checks, approved support access and final integrated security testing remain open.
|