KNOWLEDGE BASE

Embedded Views Fail to Load After Updating to Chrome 80


Published: 10 Jan 2020
Last Modified Date: 21 Feb 2020

Issue

When attempting to embed a Tableau viz on a page which is not from the same domain as Tableau server, the viz does not load in Chrome 80 or later. 
 
For example:
If Tableau Server is hosted on the domain site.com (or on a subdomain of site.com like mytableauserver.site.com), the following example domains will:
 
Embedded views will NOT load
My.othersite.com
My.unique.othersite.com
 
Embedded views will load as expected
My.site.com
My.unique.site.com

Environment

  • Tableau Server 2019.4.1, 2019.3.3, 2019.2.7, 2019.1.11, 2018.3.13, 2018.2.16, 2018.1.19, 10.5.22, 10.4.23 and all earlier versions
  • Chrome 80 and higher
  • Embedded Views

Resolution

Tableau has made a change to our latest maintenance release to support the way Chrome 80+ handles cookies, and released the attached scripts to change the configuration of existing versions to support Chrome 80+. However, due to differences in cookie handling between Chrome 80+ and Safari 12, the changes in the newest maintenance release are incompatible with Safari 12. 
Because of this, Tableau recommends using the attached configuration scripts (Option 1 below). Review all options to determine which one best suits your environment.

All versions and operating systems:

Ensure that SSL is enabled on your Tableau Server, and on any web page that contains Tableau embedded views, and clear all cookies after making the below changes.  Without taking this step, the changes will not take effect and embedded views will still fail to load on Chrome 80+.



Option 1: Run the attached configuration scripts on versions of Tableau released before January 2020 (Best option in most cases). 

Linux:
On each node in the Tableau Server cluster
  1. Download the attached script SetSameSiteNone-Linux.sh
  2. Change directory to the directory you downloaded the script to.
  3. Change it to executable: sudo chmod +x  SetSameSiteNone-Linux.sh
  4. Run the script to update the Tableau Gateway configuration: sudo ./SetSameSiteNone-Linux.sh
    • If you do SSL Offloading (SSL on a Load Balancer/Proxy and not on Tableau Server), run the script with SSLOFFLOAD: sudo ./SetSameSiteNone-Linux.sh SSLOFFLOAD
  5. Perform a restart: tsm restart
Windows with Tableau Server 2018.2 and newer:
On each node in the Tableau Server cluster
  1. Download the attached script SetSameSiteNone-TSM.cmd
  2. In an Administrative command prompt, change directory to the directory you downloaded the script to.
  3. Run the script to update the Tableau Gateway configuration:  SetSameSiteNone-TSM.cmd
  • If you do SSL Offloading (SSL on a Load Balancer/Proxy and not on Tableau Server), run the script with SSLOFFLOAD: SetSameSiteNone-TSM.cmd SSLOFFLOAD
  1. Perform a restart: tsm restart
Windows with Tableau Server 10.4 through 2018.1:
On each node in the Tableau Server cluster
  1. Download the attached script SetSameSiteNone-Tabadmin.cmd
  2. In an Administrative command prompt, change directory to the directory you downloaded the script to.
  3. Run the script to update the Tableau Gateway configuration: SetSameSiteNone-Tabadmin.cmd
  • If you do SSL Offloading (SSL on a Load Balancer/Proxy and not on Tableau Server), run the script with SSLOFFLOAD: SetSameSiteNone-Tabadmin.cmd SSLOFFLOAD
  1. Perform a restart: tabadmin restart
Note: if you apply this workaround and then upgrade to another version older than 2019.4.2, 2019.3.4, 2019.2.8, 2019.1.12, 2018.3.14, 2018.2.17, 2018.1.20, 10.5.23, or 10.4.24 you will need to re-apply this workaround as the configuration file it updates will get re-written during the upgrade.  For the listed versions and newer the scripts will no longer be needed. 
 

Option 2: Upgrade to the latest maintenance releases of Tableau (If you have no Safari 12 users in your environment, and need a fix which is in the latest maintenance release.) 


Upgrade to Tableau Server 2019.4.2, 2019.3.4, 2019.2.8, 2019.1.12, 2018.3.14, 2018.2.17, 2018.1.20, 10.5.23, 10.4.24 or a newer version. Click here for downloads of current and previous versions of Tableau Server: Tableau Server Downloads and Release Notes. For more information on current releases, see Upgrade Tableau Server and Server Upgrade.


Option 3: Configure Chrome 80 to revert to pre-Chrome 80 cookie handling behavior (if you prefer to configure Chrome rather than Tableau Server.)

See the following Chrome enterprise policy settings pages to revert back to pre-Chrome 80 behavior: With this change you do not need to immediately update Tableau Server.  However, once all your applications support SameSite and you have updated Tableau Server we recommend removing this policy.

Cause

Changes to the way Chrome 80 handles cookies have made it incompatible with older versions of Tableau Server. 
Newer versions of Tableau Server will work correctly with Chrome 80, but not Safari 12, as there is a difference in the way these two browsers handle the SameSite cookie attribute. 
Did this article resolve the issue?