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 | ||
| Steps To Reproduce | In an instance activated with 1 CU limit: 1. Log in with Openbravo user (session 1) 2. In another browser log in with Openbravo user (session 2) -> Warn about CU limit reached is displayed, but log in is allowed with only access to System Admin role 3. Without logging out, close browsers with session 1 and 2 4. Wait 3 minutes 5. Log in with a user that has NO access to System Admin -> ERROR: Login is rejected EXPECTED: Login should be allowed because sessions 1 and 2 should have been kicked out because they were abandoned for more than 2 minutes |
||
| Revision | 2018-02-15 12:11 by alostale | ||
| Steps To Reproduce | In an instance activated with 1 CU limit: 1. Log in with Openbravo user (session 1) 2. In another browser log in with Openbravo user (session 2) -> Warn about CU limit reached is displayed, but log in is allowed with only access to System Admin role 3. Without logging out, close browsers with session 1 and 2 4. Wait 3 minutes 5. Log in with a user that has NO access to System Admin -> ERROR: Login is rejected EXPECTED: Login should be allowed because sessions 1 and 2 should have been kicked out because they were inactive for more than 2 minutes |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |