T13.5: verify an auto-disable reads clearly in the admin console (D18)

No UI change. The existing Activity log card already renders a sync disable
legibly: system:okta_sync / user deprovisioned by sync / user / <name> /
okta_status: SUSPENDED|MISSING. tests/okta_sync_ui_check.py runs the real sync
on a throwaway database and reads the real page at 1440px and 390px (28/28):
rows, search, filter, no sideways scroll, no JS errors, and the disabled
account refused on its next request. Does not depend on CR-019's usage card.
This commit is contained in:
2026-10-16 11:36:38 -07:00
parent f30989d4b8
commit 763ab8d98d
2 changed files with 163 additions and 2 deletions

View File

@@ -243,13 +243,21 @@ build it in this task; log it instead if it's tempting to add.
**Done when:**
- [ ] an auto-disabled account's audit entry is visible and legible in the
- [x] an auto-disabled account's audit entry is visible and legible in the
existing admin UI without special-casing
- [ ] nothing here silently assumes `CR-019`'s activity view exists yet — this
*(2026-10-16: run on the PC against the real page, 1440px and 390px, `tests/okta_sync_ui_check.py` 28/28. The admin Activity log card reads: Who `system:okta_sync`, Action `user deprovisioned by sync`, Type `user`, Item the username, Detail `okta_status: SUSPENDED, via: okta_sync` (a person missing from Okta reads `okta_status: MISSING`). Search for `okta_sync` and the User accounts filter both find the rows. No sideways scroll, no JavaScript errors. The disabled account is refused on its very next request; an account still active in Okta is not. A project super user does not see these rows: they belong to no project, so only admins do, the same as other user-management events. No code in `html/` changed.)*
- [x] nothing here silently assumes `CR-019`'s activity view exists yet — this
must work standalone
*(2026-10-16: the check reads only the Activity log (AuditLog) card. The new Activity & usage card is on the page but is not read.)*
---
**No UI was built.** The existing card renders the new rows legibly as is. Two
things you might expect and did not get, both on purpose: no admin email on an
auto-disable (D18 calls it a fast-follow; not built, not logged as a new item
because D18 already names it), and no per-user history view in the User
Directory (it has none today, and the task says not to build one).
### T13.6 — D18: verification
- **Items:** `D18`