Session Configuration (Solution Manager Administration Tool, Design Studio, Scheduler, Diagnostic & Monitoring Tool)¶
Maximum Session Timeout¶
You can configure the maximum session timeout in the Solution Manager Administration Tool, Design Studio, Scheduler, and Diagnostic & Monitoring Tool web applications.
Important
This is not an inactivity timeout and it will be applied even when the user is active.
This feature is disabled by default and the following configuration parameter is provided:
session.maxTimeToLive=0
Note
You can set this parameter in the following configuration files:
conf/solution-manager-web-tool/SMAdminConfiguration.properties in the
Solution Manager Administration Tool,
conf/design-studio/DesignStudioBackend.properties in the
Design Studio,
conf/scheduler-webadmintool/ConfigurationParameters.properties
in Scheduler, and resources/apache-tomcat/webapps/diagnostic-monitoring-tool/WEB-INF/classes/ConfigurationParameters.properties in Diagnostic & Monitoring Tool.
You can specify the time unit in hours, minutes or seconds (minutes will be used by default). The following examples set 1-hour timeout using different time units:
session.maxTimeToLive=3600s(seconds).session.maxTimeToLive=60m(minutes).session.maxTimeToLive=60(minutes will be used if the time unit is not specified)session.maxTimeToLive=1h(hours).
In order to disable this feature, you can use negative or zero values.
Idle Session Timeout¶
User inactivity timeout can also be configured for these 2 web applications: Design Studio and Scheduler.
The property server.servlet.session.timeout sets an inactivity time for the session, meaning the time the session can remain inactive before it is considered expired. This time is counted from the user’s last interaction with the application, such as sending a request to the server.
If the user is performing actions that generate requests to the server within the specified time in server.servlet.session.timeout, the session will not expire. However, if there is no user interaction within that time, the session will be deemed inactive and expire.
Note
You can set this parameter in the following configuration files:
conf/design-studio/DesignStudioBackend.properties in the
Design Studio and
conf/scheduler-webadmintool/ConfigurationParameters.properties
in Scheduler.
By default, the configuration parameter has a value of 2 hours:
server.servlet.session.timeout=2h
You can specify the time unit in hours, minutes, seconds or milliseconds (milliseconds will be used by default). The following examples set 1-hour timeout using different time units:
server.servlet.session.timeout=3600000(milliseconds will be used if the time unit is not specified).server.servlet.session.timeout=3600s(seconds).server.servlet.session.timeout=60m(minutes).server.servlet.session.timeout=1h(hours).
Single-User Concurrent Sessions Control¶
By default, a user can open multiple sessions in Solution manager Administration Tool and Diagnostic & Monitoring tool. For example, a user can log in to Solution manager with the same credentials from two browsers (or two computers).
To enforce that a user is only logged in from one place at the time, do this:
Add this property to the following configuration files:
concurrent-session-control.enabled=true
Installation of Solution Manager:
Solution manager Administration Tool:
<SOLUTION_MANAGER_HOME>/conf/solution-manager-web-tool/SMAdminConfiguration.properties.Diagnostic & Monitoring tool:
<SOLUTION_MANAGER_HOME>/resources/apache-tomcat/webapps/diagnostic-monitoring-tool/WEB-INF/classes/ConfigurationParameters.properties.
Installation of Denodo Platform:
Diagnostic & Monitoring tool:
<DENODO_HOME>/resources/apache-tomcat/webapps/diagnostic-monitoring-tool/WEB-INF/classes/ConfigurationParameters.properties.
Important
When single-user concurrent session control is enabled, only one session per user is allowed. If the user already has a session and opens another one, first session will be closed. Also, you do not need to enable this restriction in all the applications; you can do it only in some of them.
Restart the applications in which you did this change.