Bug 857438
| Summary: | Create a way to let GUI session timeout be configurable | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | Rafael Chies <rchies> |
| Component: | UI | Assignee: | Jirka Kremser <jkremser> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | JON 3.1.0 | CC: | hrupp, jkremser, jpviragine, jshaughn |
| Target Milestone: | ER01 | Keywords: | FutureFeature |
| Target Release: | JON 3.2.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-01-02 20:43:29 UTC | Type: | Feature Request |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Rafael Chies
2012-09-14 12:38:05 UTC
There are 3 possible ways to go: 1) To provide the same behavior for all RHQ nodes withing the RHQ cluster. I.e. to have a possibility to change the value of the session timeout in the system settings. 2) To have the same session timeout for one RHQ server. The value would be stored in the rhq-server.properties file => no UI change 3) And the finest graded - to allow each user to set its own value and store it in the user's prefs. This would require a new UI for editing it. Perhaps some parts of test page could be reused. Also there are two ways of implementing the change propagation. In other words, what happens if someone changes the value. Should the change be considered after next login (a) or immediately (b)? I've made a prototype using the "1a" approach (using sys. settings and change happens after next login). The default value and at the same time the smallest possible value is 1 hour and it is unbounded (if an extra large value is typed in, it is set to 24 days (this is what Integer.MAX_VALUE of milliseconds is)) The another story is the testability. Most of the logic is in the UserSessionManager (coregui), so it is not testable by our integration tests. What can be used is the sahi. Since the minimal value is 1 hour, it is a bad idea to wait 1 hour and sahi has no means to fake the value in the db to be some lover value(in the db, the duration is stored as milliseconds). Perhaps the GWT Arquillian extension [1] could be used for this purpose. Simple GWT unit tests won't work because we need a little bit of contextual information there. [1] http://arquillian.org/blog/2013/02/26/arquillian-extension-gwt-1-0-0-Alpha1/ master 334d2167e I was manually testing it also for JSF charts commit 5cb483d45cfd88ec6ad61e1c8dfb31126e572ed5
Author: Jay Shaughnessy <jshaughn>
Date: Wed Apr 10 16:51:51 2013 -0400
Add a dbupgrade step for this. schema now at 2.132. Also, add a little
more protection when setting the session timeout.
As this is MODIFIED or ON_QA, setting milestone to ER1. As this is MODIFIED or ON_QA, setting milestone to ER01. *** Bug 535380 has been marked as a duplicate of this bug. *** *** Bug 1070248 has been marked as a duplicate of this bug. *** |