Description of problem: Even after setting UserSessionTimeOutInterval value, automatic logout does not always happen after the set period for inactivity. It seems to take much longer than the time set by the UserSessionTimeOutInterval parameter.
AFAIK: UserSessionTimeOutInterval is not exactly (or not only) the time-out interval - it is (also) used as the frequency in which the engine checks all of its sessions, and invalidates (time-outs) the "old" idle ones. So the actual session time-out can potentially be up to: UserSessionTimeOutInterval x 2 Example: UserSessionTimeOutInterval = 1 minute. time event ======== ===== 12:00:00 engine is checking for "old" idle sessions. 12:01:00 engine is checking for "old" idle sessions. 12:02:00 engine is checking for "old" idle sessions. 12:03:00 engine is checking for "old" idle sessions. ... 12:30:00 engine is checking for "old" idle sessions. 12:30:01 *** session "aaa" starts *** [session "aaa" performs no requests to the engine (i.e. it is practically idle)] 12:31:00 engine is checking for "old" idle sessions. [session "aaa" is idle for 59 seconds, 59 seconds < 1 minute -> session "aaa" is still considered "active", so it cannot be invalidated] 12:32:00 engine is checking for "old" idle sessions. [session "aaa" is idle for 1 minute + 59 seconds, 1 minute + 59 seconds > 1 minute -> session "aaa" is considered an "old" idle session -> it is being invalidated. so even though the session time-out is set to be 1 minute, session "aaa" remained valid for almost (1 minute x 2 =) 2 minutes.
ok, is6.
This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2014-0038.html