T13.11: session limit defaults to 8 hours (D25)

This commit is contained in:
2026-10-17 13:25:58 -07:00
parent 2c199f6f3f
commit 4fc6e8a01b
7 changed files with 108 additions and 7 deletions

View File

@@ -313,7 +313,7 @@ introduce a path that swallows the client's error and proceeds anyway.
## Wave 13 exit criteria
- [ ] `AUTH_SESSION_HOURS` defaults to 2, documented
- [x] `AUTH_SESSION_HOURS` defaults to 8, documented (D25 replaced the 2 hours in this line; T13.1's idle timer is still held back)
- [x] the sync job runs on a schedule and correctly disables accounts Okta no
longer shows as active
- [x] every auto-disable is individually audited with a clearly non-human actor
@@ -463,3 +463,17 @@ console of `wp_api` (no `docker compose exec` prefix). `promote` changes an exis
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.
## T13.11: D25 the session limit is 8 hours
**Item:** D25 (`docs/waves/decisions-2026-10-16.md`).
**Done when:**
- [x] `AUTH_SESSION_HOURS` defaults to 8 in `server/auth.py`, `docker-compose.yml`, `server/.env.example`, `DEPLOY-login-portal.md` (`tests/session_default_check.py`)
- [x] the token expiry and the cookie max-age follow it; a set value overrides it
- [x] mutation check: putting the default back to 12 makes the test fail
- [x] the wave 13 exit criterion that said 2 is updated
Effect on the live system: after the next deploy, sessions last 8 hours instead of 12. To get the same result
before a deploy, set `AUTH_SESSION_HOURS` to `8` in the Portainer stack variables.