Project:
| View Revisions: Issue #37928 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0037928: sys admin sessions created after reaching CU limit are not automatically kicked out | ||
| Revision | 2018-02-15 12:30 by alostale | ||
| Description | After concurrent users limit is reached, only users with System Admin role are allowed to log in the application. When this limit is reached, before rejecting new logins, it is checked if there are logged in session that were abandoned for the last 2 minutes and if so they are kicked out so log in is accepted. System Admin sessions created in this situation are not automatically kicked out, so they only get deactivated releasing its CU after manual log out or after Tomcat timeout. They should be kicked out also if they were inactive for 2 minutes. |
||
| Revision | 2018-02-15 12:11 by alostale | ||
| Description | After concurrent users limit is reached, only users with System Admin role are allowed to log in the application. When this limit is reached, before rejecting new logins, it is checked if there are logged in session that were inactive for the last 2 minutes and if so they are kicked out so log in is accepted. System Admin sessions created in this situation are not automatically kicked out, so they only get deactivated releasing its CU after manual log out or after Tomcat timeout. They should be kicked out also if they were inactive for 2 minutes. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |