Tableau connector
This page describes how to configure and use the Tableau connector
The Tableau connector enables provisioning and deprovisioning with the Tableau.com visual analytics platform. The connector uses the Tableau REST API for integration.
Create / modify user
✅
Suspend user (site role set to Unlicensed)
✅
Resume user (site role set to ExplorerCanPublish)
✅
Delete user
✅ soft delete — the user is set to Unlicensed, not removed
Assign user to groups
✅ the group must already exist in both Tableau and OpenIAM
Create / delete groups in Tableau
❌
Reset password
❌
Bulk user import / synchronization
✅
Test connection
✅
Use cases
Provisioning and deprovisioning Tableau Cloud site users from OpenIAM.
Driving Tableau group membership from OpenIAM entitlements (for groups that already exist in Tableau).
Importing Tableau users into OpenIAM for visibility and access review.
Versions and compatibility
The end application is Tableau Cloud (formerly Tableau Online) or Tableau Server, reached over the Tableau REST API.
Platform
Tableau Cloud, Tableau Server
Interface
Tableau REST API, version 3.2
Host
The managed system's URL — your Tableau pod, for example https://prod-apsoutheast-b.online.tableau.com
Site
SITE_CONTENT_URL, a managed system attribute, selects which Tableau site the connector acts on
Authentication
Sign-in at /api/3.2/auth/signin, which returns a token
Prerequisites
A Tableau service account for the connector to communicate with Tableau. Begin by creating an account in Tableau and logging in.
The Tableau host URL (e.g.,
https://your-site-name.tableau.com) and theSITE_CONTENT_URLof the site you want to connect to.
Installing the connector
In a Kubernetes deployment, the connector is deployed as part of OpenIAM. In an RPM environment, run it with the connector service unit (openiam-connector@tableau-connector-rabbitmq) or as a standalone JAR — see Connectors via RPM.
Starting, stopping, and restarting
RPM (systemd)
systemctl start|stop|restart openiam-connector@tableau-connector-rabbitmq
Kubernetes
kubectl rollout restart the connector deployment.
Command-line parameters and properties
The connector is a Spring Boot application. Its defaults ship inside the jar, and you override them in either of two places:
An external property file, read at
${confpath}/conf/properties/tableau-connector-rabbitmq.properties. The file is optional, andconfpathis itself a system property, set with-Dconfpath=/data/openiam/.Directly on the command line, as
-Darguments, which win over the file.
org.openiam.connector.queue
TABLEAU_Connector_1_Request
Must match the connector record in OpenIAM.
org.openiam.update.site.role
false
When true, the connector also updates the user's Tableau site role during provisioning; when false, site roles are left unchanged.
org.openiam.update.site.role
false
Whether the connector updates a user's Tableau site role when it updates the user
The connection details themselves are not set here — they are managed system parameters, covered under Configuring the managed system.
Verifying the connector is running
Open Provisioning → Managed system and find the Tableau row. Its Running connector status turns green and names the connector instance that answered; No active connectors found means the connector is not reachable on its queue.
Click Test Connection — it must return success.
In the RabbitMQ management console, confirm the TABLEAU_Connector_1_Request queue exists and has a consumer.
At this point, the connector should be successfully configured.
Troubleshooting
Cannot authenticate into a new site via the API
Admin user still uses "Tableau with MFA"
Change the admin user's authentication method to Tableau on the site's Users tab.
Group assignment doesn't happen
Group missing on one side
The group must exist, with a matching name, in both Tableau and OpenIAM.
Deleted users still appear in Tableau
Soft delete by design
Delete sets the user's site role to Unlicensed; the account is not removed from the site.
Display name changes don't apply
Tableau locks the display name
Once set during registration, the display name cannot be changed via OpenIAM or the Tableau UI.
Site role changes don't apply
Site-role updates disabled
Set org.openiam.update.site.role=true and restart the connector.
Group create or delete reports success but nothing changes
Group-object operations are stubs
Both return SUCCESS without calling Tableau. Create the group in Tableau first, then assign users to it.
If the connection is not established, possible causes and troubleshooting steps can be found in this document. See also the connector error-code reference.
Registering the connector in OpenIAM
Register the connector under Provisioning → Connectors and attach it to the managed system — see Registering the connector.
Configuring the managed system
Configure the Managed System and associate the connector with it.

Enter the Tableau host URL (e.g.,
https://your-site-name.tableau.com).Enter your Tableau login credentials.
Enter the value of
SITE_CONTENT_URLfor the site you want to connect to.
Both values are visible in the address bar once you are signed in to the site. A Tableau Cloud URL reads:
The site content URL is the segment after /#/site/, and it is not the site's display name — it carries a generated suffix, so copy it from the address bar rather than typing the name you gave the site.
You can create multiple sites in Tableau. To do this, go to the Cloud Management portal and create a new site.
Attribute mapping and policy map
Map the user attributes to be written to Tableau in the managed system's policy map. Behavior specific to Tableau:
Once a user is added to Tableau—either through OpenIAM or the Tableau UI—their email address will initially appear in both the Username and Display Name columns. When the user registers via the Tableau invitation link, they will be prompted to set their password, first name, and last name. After completing registration, the Display Name is updated accordingly.
To assign a user to a group, the group must exist in both Tableau and OpenIAM. The connector compares group names in both systems, and if a match is found, the group is assigned to the user.
Reconciliation and synchronization
The connector supports bulk user import — configure a synchronization against the managed system as described in Configuring synchronization.
Last updated
Was this helpful?