Loading

Cannot Control Tableau Session Timeout with LWC Embedding in Salesforce

Date de publication: Jul 16, 2026
Description

When Tableau View LWC is embedded in Salesforce, it is not possible to control or shorten the Tableau Cloud or Tableau Server session timeout from either Salesforce or the Tableau View LWC configuration. As a result, the Tableau session may remain active even after a user signs out of Salesforce.

In most deployments, this is not an issue because embedded Tableau content is typically accessed in a non-shared environment, where each user has their own device and browser session.

However, if embedded views are accessed from a shared environment (for example, shared devices or shared browser), users should be securely signed out between sessions to prevent subsequent users from reusing an existing Tableau session.

Cause

  • Tableau Cloud and Tableau Server enforce session management, including the idle session timeout, as a server-side security control. The session timeout cannot be configured or overridden by Salesforce or the Tableau View LWC.
  • Tableau View LWC does not provide a built-in sign-out mechanism for the embedded Tableau session.
  • After successful authentication, Tableau stores the session in an HttpOnly session cookie. Because HttpOnly cookies cannot be accessed or deleted by client-side JavaScript, neither Salesforce nor the Tableau View LWC can directly terminate the Tableau session.
Résolution

Use these workarounds to require more frequent re-authentication or to end sessions sooner, depending on your deployment.

Workaround 1 (Only Tableau Server): Control session timeouts

The TSM commands that control session timeouts apply only to self-hosted Tableau Server. They do not apply to Tableau Cloud.
(wgserver.session.idle_limit, wgserver.session.lifetime_limit, wgserver.session.apply_lifetime_limit)
For details, see Changing the User Session Timeout on Tableau Server.

Note: Tableau Cloud enforces a fixed idle session timeout of two hours as a platform-level security control. Site or cloud administrators cannot change this setting. For details, see User Security.

Workaround 2: Shorten the Salesforce session timeout and use JWT token authentication for SSO

Shorten the Salesforce session timeout to force users to re-authenticate with Salesforce. Each page load regenerates the JWT. Re-authentication with Salesforce produces a new JWT and starts a new Tableau session.

For details, see:

Workaround 3: Delete cookies manually or automatically using the browser

If JWT token authentication fails because no valid Tableau Cloud or Tableau Server user exists, a previous Tableau session may persist after Salesforce logout due to the Tableau HttpOnly session cookie.

Use one of the following actions.

  1. Prevent affected users from accessing the Tableau View LWC page in Salesforce-side.
  2. Clear the Tableau session cookie to terminate the Tableau session before logging in to Salesforce. 

 

Browsers can remove cookies manually or automatically*:

 

*Although we make every effort to ensure links to external websites are accurate and up to date, Tableau cannot take responsibility for content maintained by external providers. Contact the external site for questions about its content.

Numéro d’article de la base de connaissances

005388971

 
Chargement
Salesforce Help | Article