Bug 1886819 - User session limit is breaking numerous poorly designed systems
Summary: User session limit is breaking numerous poorly designed systems
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 5.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent vote
Target Milestone: ---
Assignee: Jeff Fearn 🐞
QA Contact: Jeff Fearn 🐞
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-09 13:05 UTC by Jeff Fearn 🐞
Modified: 2020-10-09 16:16 UTC (History)
3 users (show)

Fixed In Version: 5.0.4-rh49
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-09 16:16:53 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1886829 0 unspecified NEW Reinstate session limits 2021-10-21 00:03:07 UTC

Description Jeff Fearn 🐞 2020-10-09 13:05:59 UTC 
Description of problem:
The session limit introduced in Bug 1854250 is breaking numerous poorly designed applications. We need to turn this off for a release or two and allow these users to fix their broken systems.

If you are one of the people affected you should move to using API keys.

Version-Release number of selected component (if applicable):
5.0.4-rh48

How reproducible:
Easy

Steps to Reproduce:
1. Create a bot
2. do not use api_keys
3. do not take any effort to manage your sessions
4. login every call

Actual results:
You hit the session limit.

Expected results:
You don't hit the limit.

Additional info:
This will be a short reprieve and users are expected to either switch to api_keys or handle sessions properly.
Comment 2 Alasdair Kergon 2020-10-09 15:01:02 UTC 
Temporary workaround is to login through the UI, go to preferences, session tab and 'Log out all other sessions'.

https://bugzilla.redhat.com/userprefs.cgi?tab=sessions
Comment 4 Jeff Fearn 🐞 2020-10-09 16:16:53 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.