Skip to main content
Version: current [26.x]

Idle Session Timeout Enterprise

Idle Session Timeout automatically logs users out of the Dremio console after a configurable period of inactivity.

By default, this feature is disabled. However, all user sessions have a maximum lifetime defined by the token.expiration.min support key, which defaults to 30 hours (see Support Settings). When Idle Session Timeout is disabled, sessions remain active until this maximum lifetime is reached or the user manually logs out.

Enable Idle Session Timeout​

  1. Click in the side navigation bar.
  2. Select Preferences from the settings sidebar.
  3. In the Idle Session Timeout setting, specify the timeout duration and select the unit (minutes or hours). The default timeout period is 2 hours.
  4. Toggle the Idle Session Timeout switch to enable the feature.

What Counts as Activity​

Actions that involve direct user input — such as moving or clicking the mouse, scrolling the mouse wheel, typing on the keyboard, or unlocking the screen — reset the inactivity timer. Actions that occur outside the browser or without direct user input do not reset the timer. For example, opening a new browser tab, JavaScript activity without user input, and moving the mouse outside the browser window are not counted as activity.

Multi-Tab Behavior​

Idle Session Timeout is synchronized across all open Dremio console tabs that share the same session. If a user is active in any tab, the session stays alive across all tabs. If the user remains idle across all tabs, they are logged out when the timeout expires, and any tab prompts them to log in again on the next interaction.

After Timeout​

When a session times out, the user is not immediately redirected. Instead, the login page appears on the next user interaction, such as clicking, navigating, or making a data request. A timeout affects all open tabs, regardless of how many are open.

Running queries are unaffected by a timeout and continue to completion. Results remain available on the Jobs page. Unsaved SQL editor tab contents are also preserved — after logging back in, your SQL editor tabs and their contents are restored.

Scope​

Idle Session Timeout applies only to interactive sessions in the Dremio console. It does not affect ODBC or JDBC connections, Arrow Flight sessions, REST API sessions, or scheduled jobs and Reflection refreshes.

If you use a BI front-end such as Tableau, session timeout for that tool must be configured within the BI product itself.