Difference between revisions of "Administration console timeout"

From Swivel Knowledgebase
Jump to: navigation, search
 
(Changing the timeout value)
 
(2 intermediate revisions by 2 users not shown)
Line 19: Line 19:
 
= Changing the timeout value =
 
= Changing the timeout value =
  
This is controlled on each Swivel instance in the file ''web.xml''
+
This is controlled by a setting in the following file:
  
For a Swivel virtual or hardware appliance:
+
/usr/local/apache-tomcat/webapps/sentry/WEB-INF/web.xml
  
/usr/local/webapps/pinsafe/WEB-INF/web.xml
+
It can only be edited from the appliance command line: please contact Swivel Secure support (teamsupport@swivelsecure.com) to arrange access.
 
 
 
 
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 How To Guide | WinSCP]] to edit the file:
 
  
 
Edit the ''session-timeout'' value
 
Edit the ''session-timeout'' value
  
 
   <session-config>
 
   <session-config>
          <session-timeout>30</session-timeout>
+
      <session-timeout>30</session-timeout>
      </session-config>
+
  </session-config>
  
 +
= 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.

Latest revision as of 13:15, 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 by a setting in the following file:

/usr/local/apache-tomcat/webapps/sentry/WEB-INF/web.xml

It can only be edited from the appliance command line: please contact Swivel Secure support (teamsupport@swivelsecure.com) to arrange access.

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.