Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0015688
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Openbravo ERP] A. Platformmajorhave not tried2011-01-17 20:302022-02-01 08:08
ReporterjohnfandlView Statuspublic 
Assigned ToTriage Platform Base 
PrioritynormalResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionpiSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0015688: Session Timeout by Role

DescriptionOpenbravo 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."
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.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
There are no notes attached to this issue.

- 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


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker