Focal Point
[SOLVED] SESSION_EXPIRATION

This topic can be found at:
https://forums.informationbuilders.com/eve/forums/a/tpc/f/7971057331/m/1971020413

January 16, 2009, 01:20 AM
<Radha>
[SOLVED] SESSION_EXPIRATION
SESSION_EXPIRATION: If this parameter is set to 20 mins, does it imply that irrespective of the user perfroming some action, once the session is initiated, the session is going to expire after 20 mins or does it mean that the session is active for another 20 mins every time the user performs some action ?
(I am currently working on an application which has a launch page for a set of reports, so this scenario pops up if the user selects one report and then it is left idle for sometime. Then he comes and runs an another report from the launch page)

This message has been edited. Last edited by: Kerry,
January 16, 2009, 03:14 AM
<JG>
quote:
SESSION_EXPIRATION

This is nothing to do with an enduser.
It relates only to the WebFOCUS server console.

If endusers are getting timeouts in a standard WebFOCUS session then check the value of WF_COOKIE_EXPIRATION in the WebFOCUS administration console (not the server console).
If the problem is in dashboard check USER_MAX_INACTIVE in web.xml.

Any timeout means if the user takes no action the timeout comes into effect. if the user does perform some action the timeout is reset.
January 18, 2009, 08:16 PM
StuBouyer
Also be aware that the application server may have it's own timeouts.

Apache Tomcat should have reasonable timeouts (5 hours plus) but New Atlanta ServletExec used to default to 30 minutes.

Cheers

Stu


WebFOCUS 8.2.03 (8.2.06 in testing)
January 18, 2009, 11:54 PM
<Radha>
Thank you JG and STU.
January 19, 2009, 09:13 AM
<JG>
Radha,

As I said SESSION_EXPIRATION has TOTALLY nothing to do with your problem.

A user session will stay active as long as the user is logged on to WebFocus and the
WebFOCUS cookie has not expired.

This is controlled by the WF_COOKIE_EXPIRATION cookie as I explained.

If a user logs off the cookie expires and no further reports can be run unless

a) The user logs on again.
or
b) You pass the logon id and password as part of your URL.

If you set WF_COOKIE_EXPIRATION to a specific time then that deletes the cookie
and effectively logs off, however if you pass the logon id and password as part of your URL then that effectively does an automatic logon.
January 20, 2009, 01:03 AM
<Radha>
Thank you JG. I am not able to delete the other discussion currently, will do it once possible.