Description of problem: For bug 1886819 we disabled the session limit enforcement to give users time to fix their systems, now we need to re-enable them. Version-Release number of selected component (if applicable): n/a How reproducible: Easy Steps to Reproduce: 1. try and create 43 sessions as a single user Actual results: You can. Expected results: You can't. Additional info:
1. login to web UI 2. go to Sessions preferences tab 3. run login script in a shell $ perl bug_1886829.pl Login 1 OK Login 2 OK ... Login 40 OK Login 41 OK Login 42 NOK The account you are using has too many current logins. The maximum number of concurrent logins is 42 and you have 42. You will need to wait until enough sessions expire before you can login again. Sessions expire after being unused for 7 days. All sessions are removed during an upgrade regardless of age. If you are using the API you might consider using API_KEYs instead of logging in. If you don't want to use API_KEYs then you need to logout to prevent being locked out. at bug_1886829.pl line 62. 4. Refresh Sessions preferences tab "You have 42 sessions. Display limited to most recent 20." 5. Click "Log out all other sessions" button
This change is now live. If there are any issues, do not reopen this bug. Instead, you should create a new bug and reference this bug.