Error "This content cannot be displayed in a frame" Viewing Embedded Dashboard in SharePoint

Published: 14 Dec 2015
Last Modified Date: 25 Apr 2016


When viewing a dashboard embedded in a SharePoint page, where both Tableau Server and SharePoint are using the same SAML/ADFS authentication, the dashboard might not load and the following error message might occur:

This content cannot be displayed in a frame
To help protect the security of information you enter into this website, the publisher of this content does not allow it to be displayed in a frame.


  • Tableau Server 9.0.4 and later versions
  • SharePoint
  • SAML authentication via ADFS


If clickjacking protection is not enabled, run the following commands:
tabadmin set wgserver.saml.iframed_idp.enabled true
tabadmin config
tabadmin restart



Tableau Server with SAML authentication is SP-initiated only. Even though SharePoint and Tableau Server are using the same ADFS server for authentication, Tableau Server authentication does not occur when logging in through SharePoint.

Under normal circumstances, a sign in button is displayed where the dashboard is embedded, which allows for SP-initiated authentication. Enabling wgserver.saml.iframed_idp.enabled removes the sign in button and forces the SP-initiated authentication to Tableau Server so that the dashboard will be displayed.

Additional Information

To test and verify this root cause:
  1. Open incognito or another private browsing session.
  2. Go to the SharePoint site and login (IdP-initiated).
  3. The Tableau embedded dashboard will not be displayed.
  4. Close the browser and open a new incognito.
  5. Go to Tableau Server first and login (SP-initiated).
  6. Then go to the SharePoint site and the dashboard will be displayed.
It might also be necessary to disable clickjack protection on Tableau Server in order to embed, or if clickjack protection is enabled, follow the proper URL syntax when constructing the embedded dashboard URL. For more information, see Clickjacking Protection in Tableau Server.
Did this article resolve the issue?