Session Configuration (Design Studio, Data Catalog, Scheduler, Diagnostic & Monitoring Tool)

Maximum Session Timeout

You can configure the maximum session timeout in the Design Studio, Data Catalog, Scheduler and Diagnostic & Monitoring Tool web applications.


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


You can set this parameter in the following configuration files: conf/design-studio/ in the Design Studio, conf/data-catalog/ in the Data Catalog, conf/scheduler-webadmintool/ in Scheduler, and resources/apache-tomcat/webapps/diagnostic-monitoring-tool/WEB-INF/classes/ 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).

To disable this feature, enter zero or a negative value.

Single-User Concurrent Sessions Control

By default, a user can open multiple sessions in Data Catalog, Design Studio and Scheduler. For example, a user can log in to Data Catalog 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:

  1. Add this property to the following configuration files:

  • Installation of Solution Manager:

    • Design Studio: <SOLUTION_MANAGER_HOME>/conf/design-studio/

    • Scheduler: <SOLUTION_MANAGER_HOME>/conf/scheduler-webadmintool/

  • Installations of Denodo Platform:

    • Data Catalog: <DENODO_HOME>/conf/data-catalog/ (Solution Manager does not include Data Catalog).

    • Design Studio: <DENODO_HOME>/conf/design-studio/

    • Scheduler: <DENODO_HOME>/conf/scheduler-webadmintool/

Consider this:

  • When this feature is enabled and a user logs in from one browser and then, from another browser, the user is allowed to log in the second time and the application closes the first session.

  • You do not need to enable this restriction in all the applications; you can do it only in some of them.

Add feedback