Enable Kerberos Delegation

Kerberos delegation enables Tableau Server to use the Kerberos credentials of the viewer of a workbook or view to execute a query on behalf of the viewer. This is useful in the following situations:

  • You need to know who is accessing the data (the viewer's name will appear in the access logs for the data source).

  • Your data source has row-level security, where different users have access to different rows.

Supported data sources

Tableau supports Kerberos delegation with the following data sources:

  • Cloudera: Hive/Impala
  • Denodo
  • Hortonworks
  • MSAS
  • Oracle
  • PostgreSQL
  • Spark
  • SQL Server
  • Teradata


Kerberos delegation requires Active Directory.

  • The Tableau Server information store must be configured to use LDAP - Active Directory.
  • The computer where Tableau Server is installed must be joined to Active Directory domain.
  • MIT KDC is not supported.
  • Delegation (Run As) service account: Grant delegation rights for this account to the target database Service Principal Names (SPNs). This account is delegated authority to access resources on behalf of the initiating source user. This account must be a user account in the Windows Active Directory domain. If your users are in a different Active Directory domain than Tableau Server and the data source, then domain trust must be configured. See Domain Trust Requirements.

Configuration process

This section provides an example of the process to enable Kerberos delegation. The scenario also includes example names to help describe the relationships between the configuration elements.

  1. On all nodes in Tableau Server, configure the Run As User to act as part of the operating system. For more information, see Enable Run As Service Account to Act as the Operating System.

  2. Tableau Server will need a Kerberos service ticket to delegate on behalf of the user that is initiating the call to the database. You must create a domain account that will be used to delegate to the given database. This account is referred to as the Run As service account. In this topic, the example user configured as the delegation/Run As account is tabsrv@example.com.

    The account must be configured with Active Directory User and Computers on a Windows Server that is connected to the user domain:

    • Open the Properties page for the Run As service account, click the Delegation tab and select Trust this user for delegation to specified services only and Use any authentication protocol.
  3. Run the following TSM command to enable Kerberos delegation:

    tsm configuration set -k wgserver.delegation.enabled -v true

  4. Run the following TSM command apply the changes to Tableau Server:

    tsm pending-changes apply

    The pending-changes apply command displays a prompt to let you know this will restart Tableau Server if the server is running. The prompt displays even if the server is stopped, but in that case there is no restart. You can suppress the prompt using the --ignore-prompt option, but this does not change the restart behavior. For more information, see tsm pending-changes apply.

  5. (Optional) Configure Tableau Server to use MIT Kerberos principal format.

    By default, Tableau Server generates Kerberos principals using the Active Directory short name. For example, if Tableau Server performs Kerberos delegation for a user in EXAMPLE.COM, with a short name EXAMPLE, then the principal name will be: user@example.

    If your database is running on Linux, you may need to adjust the auth_to_local mapping in krb5.conf. For information about editing the krb5.conf file, see Kerberos delegation multi-domain configuration. Alternatively, you can configure Tableau Server to use the full domain name for Kerberos principals by running the following commands:

    tsm configuration set -k native_api.protocol_transition_a_d_short_domain -v false --force-keys
    tsm configuration set -k native_api.protocol_transition_uppercase_realm -v true --force-keys
    tsm pending-changes apply
  6. Enable delegation for data connections:

    See also

    Troubleshoot Kerberos

Thanks for your feedback! There was an error submitting your feedback. Try again or send us a message.