Tableau is a popular analytics tool with powerful data visualization capabilities. You can access clusters in Starburst Galaxy or Starburst Enterprise platform (SEP) from the following Tableau products:
Connect Tableau products to a SEP or Starburst Galaxy cluster using one of three available connectors. Each connector requires the installation of either a JDBC or ODBC driver.
This is the recommended connector, shown as “Starburst by Starburst” in the Tableau connector list. Compared to the legacy “Other Database” JDBC or ODBC connectors, this connector offers the following features:
To use the latest connector, you must have Tableau 2024.1 or later and Trino JDBC driver 469 or later. If you have an older version of Tableau products, ask Starburst Support for access to an older version of Tableau data connector.
This is a legacy connector built for any JDBC driver, shown as “Other Database (JDBC)” in the Tableau connector list.
To use this connector, you must have a Trino JDBC driver compatible with the target Starburst server.
This is a legacy connector built for any ODBC driver, shown as “Other Database (ODBC)” in the Tableau connector list.
To use this connector, you must have a Starburst ODBC driver compatible with the target Starburst server.
Starburst continues to support the use of legacy JDBC or ODBC connectors. However, we recommend migrating to the Starburst connector for all new and existing Tableau data sources and workbooks.
Determine the connection information for your cluster, including its server name, TCP port (or default port), and your login credentials.
For Starburst Galaxy clusters, the Connection info pane provides two ways to obtain connection information:
Starting with version 1.5.0, the Starburst connector for Tableau supports OAuth 2.0 authentication.
Before using this feature, you must first create an OAuth client and write a OAuth confiiguation file.
To use OAuth 2.0 to connect to SEP, perform the following steps:
Create or register an application for Tableau integration in your identity provider, and add the following URIs to its login redirect URI list:
https://tableau.myco.com/auth/add_oauth_token
http://localhost:55555/Callback
http://localhost:55556/Callback
http://localhost:55557/Callback
http://localhost:55558/Callback
http://localhost:55559/Callback
You can reuse an existing URI created for the SEP web UI, but this is not recommended. Instead, use a public client that utilizes OAuth 2.0 authorization code flow with PKCE to avoid sharing a client secret.
Create an OAuth configuration file and save it for future use. You can use one of the following templates:
entra-id_oauth_config.xml
okta_oauth_config.xml
In these templates, pay attention to the following:
<clientIdDesktop>
is the application ID you created in step 1.<clientSecretDesktop>
in the confiiguration file.For more information about Tableau OAuth configuraton files, refer to OAuth Configuration and Usage in Tableau’s documentation.
Perform the following steps to use OAuth 2.0 to connect to Starburst Galaxy:
Create an OAuth
client
for Tableau Desktop and Prep Builder. Choose Public
as the client type and
Tableau
as the application type.
Create an OAuth configuration file for Tableau Desktop and Prep Builder. You
can use the following template:
galaxy_oauth_config.xml. Make sure that the
<clientIdDesktop>
value matches the OAuth client ID you created in step 1.
Create an OAuth
client
for Tableau Server or Tableau Cloud. Choose Public
as the client type and
Custom
as the application type, and enter
https://<your-tableau-server-or-cloud-domain>/auth/add_oauth_token
in the
Redirect URI field.
Create an OAuth configuration file for Tableau Server or Tableau Cloud. Use
the entra-id_oauth_config.xml template. Make
sure the <clientIdDesktop>
value matches the OAuth client ID you
created in step 3.
Repeat step 3 and 4 for each additional Tableau Server and Tableau Cloud site.
Is the information on this page helpful?
Yes
No