T13.11: session limit defaults to 8 hours (D25)
This commit is contained in:
@@ -94,3 +94,22 @@ status and Okta's short error code only. The SSWS token path is unchanged.
|
||||
|
||||
**Not verified:** this has been tested only against a fake Okta that follows the RFC. The
|
||||
first run against the real tenant is the real test.
|
||||
|
||||
## D25: the session limit is 8 hours for now
|
||||
|
||||
**Decided by:** Matt Mabrey, 2026-10-17. **Closes:** the 2-versus-8 question in `wave-13.md`. **Task:** T13.11.
|
||||
|
||||
**The conflict:** the wave 13 exit criteria said `AUTH_SESSION_HOURS` defaults to 2. T13.1's own text and
|
||||
the T13.1 code say 8. The shipped default on `main` was 12.
|
||||
|
||||
**Decision:** The default is **8 hours**. This replaces the exit criterion of 2 hours.
|
||||
|
||||
- `AUTH_SESSION_HOURS` defaults to 8 in `server/auth.py`, `docker-compose.yml`, `server/.env.example` and
|
||||
`DEPLOY-login-portal.md`. A value that is set still wins.
|
||||
- Until T13.1 lands, 8 hours is one flat limit from the moment of sign-in, with no sliding. Once T13.1 lands, the
|
||||
same variable is the absolute ceiling and an idle timer sits under it. The default does not change then.
|
||||
- A person who signs in at the start of a shift is signed out 8 hours later, whatever they were doing. Signing in
|
||||
again needs Okta to be reachable.
|
||||
|
||||
**Open, for wave 14:** how the limit works for a crew that is offline. `wave-14.md` sets that rule.
|
||||
**Not decided here:** the idle time (T13.1 proposes 30 minutes). It is a proposed value, not a decision.
|
||||
|
||||
Reference in New Issue
Block a user