Set up a Tableau connector
Capabilities
Resource | Sync | Provision |
---|---|---|
Accounts | ✅ | |
Groups | ✅ | |
Sites | ✅ |
Available hosting methods
Choose the hosting method that best suits your needs:
Method | Availability | Notes |
---|---|---|
Cloud-hosted | ✅ | A built-in, no-code connector hosted by ConductorOne. |
Self-hosted | ✅ | The Tableau connector, hosted and run in your own environment. |
Gather Tableau credentials
Each setup method requires you to pass in credentials generated in Tableau. Gather these credentials before you move on.
A user with the Server Administrator role in Tableau Server or Site Administrator in Tableau Cloud must perform this task.
To work with the Tableau APIs, you’ll need either an installation of Tableau Server or membership in the Tableau Developer Program, which grants you a personal Tableau Cloud sandbox.
Generate a Personal Access Token
Sign into Tableau Server or Tableau Cloud.
In the menu bar at the top of the page, click your profile image or initials and select My Account Settings from the menu.
In the Personal Access Tokens area of the page, enter a name for your new token (such as “ConductorOne integration”) and then click Create.
Carefully copy and save the newly generated token and its name.
Locate your server path and site ID
Locate your server path, which is the base URL for your Tableau server.
Locate your site ID, which is the value that appears after
/site/
in the full URL for your Tableau instance.
Examples:
For a Tableau Server instance with the URL http://SampleServer/#/site/SecurityTeam/projects
, the server path is SampleServer
and the site ID is SecurityTeam
.
For a Tableau Cloud instance with the URL https://10ay.online.tableau.com/#/site/MarketingTeam/workbooks
, the server path is 10ay.online.tableau.com
and the site ID is MarketingTeam
.
That’s it! Next, move on to the instructions for your chosen setup method.
Set up a Tableau cloud-hosted connector
To complete this task, you’ll need:
- The Connector Administrator or Super Administrator role in ConductorOne
- Access to the set of Tableau credentials generated by following the instructions above
In ConductorOne, click Connectors > Add connector.
Search for Tableau and click Add.
Choose how to set up the new Tableau connector:
Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.
If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
Click Next.
Find the Settings area of the page and click Edit.
Enter the site ID and server path into the Site ID and Server path fields.
Enter the name of the personal access token into the Access token name field.
Enter the personal access token value into the Access token secret field.
Click Save.
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
That’s it! Your Tableau connector is now pulling access data into ConductorOne.
Set up a Tableau cloud-hosted connector using Terraform
As an alternative to the cloud-hosted setup process described above, you can use Terraform to configure the integration between Tableau and ConductorOne.
See the ConductorOne Tableau integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.
Set up a Tableau self-hosted connector
To complete this task, you’ll need:
- The Connector Administrator or Super Administrator role in ConductorOne
- Access to the set of Tableau credentials generated by following the instructions above
When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.
Why use Kubernetes? Kubernetes provides automated deployment, scaling, and management of your connectors. It ensures high availability and reliable operation of your connector services.
Step 1: Configure the Tableau connector
In ConductorOne, navigate to Connectors > Add connector.
Search for Baton and click Add.
Choose how to set up the new Tableau connector:
Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.
If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
Click Next.
In the Settings area of the page, click Edit.
Click Rotate to generate a new Client ID and Secret.
Carefully copy and save these credentials. We’ll use them in Step 2.
Step 2: Create Kubernetes configuration files
Create two Kubernetes manifest files for your Tableau connector deployment:
Secrets configuration
# baton-tableau-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
name: baton-tableau-secrets
type: Opaque
stringData:
# ConductorOne credentials
BATON_CLIENT_ID: <ConductorOne client ID>
BATON_CLIENT_SECRET: <ConductorOne client secret>
# Tableau credentials
BATON_ACCESS_TOKEN_NAME: <Name of the Tableau access token>
BATON_ACCESS_TOKEN_SECRET: <Tableau access token>
BATON_SERVER_PATH: <Base URL for your Tableau server>
BATON_SITE_ID: <Tableau site ID>
See the connector’s README or run
--help
to see all available configuration flags and environment variables.
Deployment configuration
# baton-tableau.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: baton-tableau
labels:
app: baton-tableau
spec:
selector:
matchLabels:
app: baton-tableau
template:
metadata:
labels:
app: baton-tableau
baton: true
baton-app: tableau
spec:
containers:
- name: baton-tableau
image: ghcr.io/conductorone/baton-tableau:latest
args: ["service"]
imagePullPolicy: IfNotPresent
envFrom:
- secretRef:
name: baton-tableau-secrets
Step 3: Deploy the connector
Create a namespace in which to run ConductorOne connectors (if desired):
kubectl create namespace conductorone
Apply the secret configuration:
kubectl -n conductorone apply -f baton-tableau-secrets.yaml
Apply the deployment:
kubectl -n conductorone apply -f baton-tableau.yaml
Step 4: Verify the deployment
Check that the deployment is running:
kubectl -n conductorone get pods
View the connector logs:
kubectl -n conductorone logs -l app=baton-${baton-tableau}
Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the Tableau connector to. Tableau data should be found on the Entitlements and Accounts tabs.
That’s it! Your Tableau connector is now pulling access data into ConductorOne.