Skip to main content
This authentication method is deprecated and no longer supported in Curator. Please migrate to Connected Apps or another SSO method as soon as possible.
Curator no longer supports Embed Authentication using Trusted Tickets. Versions released in October 2025 or later, Trusted Tickets will no longer be supported. To ensure uninterrupted Dashboard access, you must migrate to Connected Apps or another SSO method before upgrading to those versions. For guidance on transitioning, refer to our guide on how to setup Connected Apps.
By default, if the Tableau Server workbook views which are embedded in dashboards require a login, the user will be prompted for their username and password the first time they view any Dashboard. With trusted ticket authentication enabled on the system and on the associated Tableau Server, the system will authenticate on behalf of the user. One drawback to using trusted tickets is that there is a little more overhead to authenticate on behalf of the user before showing the Dashboard. Since trusted tickets are one-time use, this authentication takes place before each and every Dashboard is shown. This functionality requires that the Tableau Server REST API is enabled which you can establish by creating a Tableau Connection.

​
Enabling Trusted Tickets (Unavailable)

This feature is no longer supported in Curator as of October 1, 2025, and is for reference purposes only.
  1. Login to the backend of your Curator instance (e.g. http://curatorexample.com/backend).
  2. Navigate to Integrations > Connections from the left-hand menu.
  3. Click on your Tableau Server from the list view.
  4. Expand the Embed Authentication Section.
  5. Select Trusted Ticket Authentication in the drop-down selection box for Which authentication type will embedded dashboards use.
  6. If you have not set up Curator as a trusted host on your Tableau Server, follow the instructions in the dialog box that appears below the enabled button.
  7. Save the Connection.
Note: The dialog box lists out a couple of different trusted hosts to add to Tableau Server. Those include the server address (Outbound IP), local address, server name and hostname. These are Curator’s best guess at which hosts requests originating from Curator will be seen by Tableau Server. Depending on your network configuration, these may not be correct by the time the request reaches Tableau Server. Adjust as needed. Note: If you use a reverse proxy or load balancer on the network between Curator and Tableau Server, DO NOT configure the reverse proxy or load balancer as a trusted host. Reverse proxies or load balancers can be configured instead as a trusted gateway if needed. However, it’s likely that you’ll need to configure the reverse proxy or load balancer to pass through specific headers so Tableau Server can tell that the request comes from Curator. Instructions for these headers can be found in Tableau’s documentation
⌘I