Logins not honoring all org unit timeout settings
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
2.12 |
Won't Fix
|
Medium
|
Unassigned | ||
3.1 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Evergreen 2.11, 2.12
We're seeing that all staff logins appear to be using the auth.staff_timeout ou setting at the top of the org tree, rather than the timeouts set further down the tree. I suspect this is also true for other login types.
For example, CONS has an auth.staff_timeout set at 14400 (4 hrs), BR1 has the timeout set at 28800 (8 hrs).
When a user with home library BR1 logs in at BR1, they are getting a timeout of 4 hours when they should be getting 8 hours.
Here are some log entries from a test system:
User 238 has home library of BR1.
open-ils.
open-ils.
No matter what user logs in, staff, opac, etc., log entries always report: "org_unit":0. I have not verified that login types other than staff get the setting at the top of the tree, but we are definitely seeing it for staff logins on our production system (2.11).
Changed in evergreen: | |
status: | New → Confirmed |
assignee: | nobody → Bill Erickson (berick) |
Changed in evergreen: | |
milestone: | 3.0.1 → 3.0.2 |
Changed in evergreen: | |
milestone: | 3.0.2 → 3.0.3 |
Changed in evergreen: | |
milestone: | 3.0.3 → 3.0.4 |
Changed in evergreen: | |
milestone: | 3.0.4 → 3.0.5 |
Changed in evergreen: | |
milestone: | 3.0.5 → 3.0.6 |
Changed in evergreen: | |
milestone: | 3.0.6 → 3.0.7 |
Changed in evergreen: | |
milestone: | 3.0.7 → 3.0.8 |
Changed in evergreen: | |
assignee: | nobody → Bill Erickson (berick) |
Changed in evergreen: | |
assignee: | Bill Erickson (berick) → nobody |
Changed in evergreen: | |
assignee: | nobody → Michele Morgan (mmorgan) |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
Fix pushed:
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ berick/ lp1693035- auth-org- settings- global
This patch solidifies the precedence order for OUS lookups during login like so:
1. Workstation org unit.
2. API org unit value.
3. Users' home org unit.
Note that this does not affect which org unit is used for permissions or for applying a ws_ou value to the user when no workstation is provided. Those are consistent w/ previous behavior.