T13.6: confirm the auto-disable audit row in the Admin Console (D18)
This commit is contained in:
@@ -316,7 +316,7 @@ introduce a path that swallows the client's error and proceeds anyway.
|
||||
- [ ] `AUTH_SESSION_HOURS` defaults to 2, documented
|
||||
- [x] the sync job runs on a schedule and correctly disables accounts Okta no
|
||||
longer shows as active
|
||||
- [ ] every auto-disable is individually audited with a clearly non-human actor
|
||||
- [x] every auto-disable is individually audited with a clearly non-human actor
|
||||
- [x] an Okta API failure of any kind changes zero accounts — verified, not
|
||||
assumed
|
||||
- [x] the sync never re-enables an account
|
||||
@@ -458,8 +458,8 @@ console of `wp_api` (no `docker compose exec` prefix). `promote` changes an exis
|
||||
|
||||
- `T13.1` (idle timeout) is held back from `main` until T14.1 lands. The exit criterion "`AUTH_SESSION_HOURS` defaults to 2"
|
||||
is not met, and it conflicts with T13.1's own text (8 hours). Matt has not chosen.
|
||||
- "Every auto-disable is individually audited with a clearly non-human actor" was not checked in the admin console
|
||||
after the live run. The code writes one `AuditLog` row with actor `system:okta_sync`, and `okta_sync_job_check.py` and
|
||||
`okta_sync_ui_check.py` verify it. Open the Admin Console and look for the `admin` row to confirm it.
|
||||
- ~~"Every auto-disable is individually audited with a clearly non-human actor" was not checked after the live run.~~
|
||||
Checked 2026-10-17: the Admin Console activity list shows one row, actor `system:okta_sync`, action "user deprovisioned
|
||||
by sync", item `admin`, detail `okta_status: MISSING, via: okta_sync`, at 11:46 AM local (18:46 UTC).
|
||||
- `D18` cannot be called fully accounted for while T13.1 is outstanding.
|
||||
- `BL-069` (a cap on one run and a last-admin guard) is open.
|
||||
|
||||
Reference in New Issue
Block a user