Difference between revisions of "Administration console timeout"

From Swivel Knowledgebase
Jump to: navigation, search
m (1 revision imported)
(Known Issues)
Line 41: Line 41:
  
 
= Known Issues =
 
= Known Issues =
 +
 +
Any change to the session timeout will only apply to new sessions, not to existing ones. Any current session will keep the timeout setting it was given when it was created.
  
 
On an upgrade of Swivel, this value will be set back to default and will need to be re-entered.
 
On an upgrade of Swivel, this value will be set back to default and will need to be re-entered.

Revision as of 13:08, 27 February 2020


Overview

The Swivel Administration console automatically logs out a user after a set period of inactivity. This time period can be changed.


Prerequisites

Swivel 3.x


Symptoms

Swivel Administration console session timeout needs to be changed.


Changing the timeout value

This is controlled on each Swivel instance in the file web.xml

For a Swivel virtual or hardware appliance:

/usr/local/webapps/pinsafe/WEB-INF/web.xml


For a Software install, this is usually

C:\Program Files\Apache Software Foundation\Tomcat 6.0\webapps\pinsafe\WEB-INF\web.xml


For Swivel virtual or hardware appliances use WinSCP to edit the file:

Edit the session-timeout value

 <session-config>
         <session-timeout>30</session-timeout>
     </session-config>


Known Issues

Any change to the session timeout will only apply to new sessions, not to existing ones. Any current session will keep the timeout setting it was given when it was created.

On an upgrade of Swivel, this value will be set back to default and will need to be re-entered.