Openbravo Issue Tracking System - Openbravo ERP | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0015688 | Openbravo ERP | A. Platform | public | 2011-01-17 20:30 | 2022-02-01 08:08 |
| Reporter | johnfandl | ||||
| Assigned To | Triage Platform Base | ||||
| Priority | normal | Severity | major | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | pi | ||||
| Target Version | Fixed in Version | ||||
| Merge Request Status | |||||
| Review Assigned To | |||||
| OBNetwork customer | |||||
| Web browser | |||||
| Modules | Core | ||||
| Support ticket | |||||
| Regression level | |||||
| Regression date | |||||
| Regression introduced in release | |||||
| Regression introduced by commit | |||||
| Triggers an Emergency Pack | No | ||||
| Summary | 0015688: Session Timeout by Role | ||||
| Description | Openbravo currently supports one global session timeout, which governs the number of minutes of inactivity before a session is automatically ended. While it is nice that we provide this flexibility, extending this flexibility to the role level would allow partners to cost-effectively expand the number of ERP users out to different user classes, by treating the roles differently. For example, a Finance role could be set to have up to 2 hours of inactivity before being automatically logged off, while an Employee role (for expenses and PO requisitions) could be set to 10 minutes. This feature allows for much more effective use of the licensed concurrent users, which will increase the number of concurrent users that customers license. It is a very nice complement to the "Casual Users" concept, and can perhaps be implemented at less cost (since no impact to Butler). "All animals are equal, but some animals are more equal than others." | ||||
| Steps To Reproduce | |||||
| Proposed Solution | 1. Add a "session timeout" (in minutes) at the role level. 2. When a user logs on to a role, capture this value in the user's session 3. The logic that governs whether or not a user's session should be automatically expired should use this value. Cutover logic (on Upgrade): 1. Initially set the role-based session timeout to the same value as the global one. 2. Keep the global one in the system, and use it as the fallback (if for some reason a valid one is not found at the role level. | ||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2011-01-17 20:30 | johnfandl | New Issue | |||
| 2011-01-17 20:30 | johnfandl | Assigned To | => alostale | ||
| 2011-01-17 20:30 | johnfandl | Modules | => Core | ||
| 2017-04-10 14:39 | alostale | Assigned To | alostale => platform | ||
| 2022-02-01 08:08 | alostale | Assigned To | platform => Triage Platform Base | ||
| There are no notes attached to this issue. |