KNOWLEDGE BASE

Viewer Credentials Option Unavailable When Publishing


Published: 04 Oct 2016
Last Modified Date: 29 Jul 2019

Issue

When publishing a workbook or data connection from Tableau Desktop to Tableau Server with Kerberos enabled, Viewer Credentials option is not available as expected. Only 'Run As User' or 'Impersonate as Run As' user options are available.

Environment

  • Tableau Desktop
  • Tableau Server 
  • MS SQL Server
  • MSAS
  • Kerberos

Resolution

Option 1

Upgrade to Tableau Desktop 2018.2.12 or a newer version. See Tableau Desktop Downloads and Release Notes for downloads of current and previous versions of Tableau Desktop. For more information on current releases, see Upgrade Tableau Desktop and Desktop Upgrade.
Once upgraded, the 'Viewer credentials' option is available for selection, under Data Sources.

Option 2

After confirming that your environment has been successfully configured for Kerberos, complete the following steps:
  1. Open Tableau Desktop and select 'Help > Settings and Performance > Clear Saved Server Sign-ins'. This will clear all old connection information from Tableau Desktop.
  2. Run the following command from a command prompt run as Administrator on the computer running Tableau Desktop:
    klist purge
    The above command will clear Kerberos user tickets off of the system.
  3. Launch Internet Explorer in Private mode, and navigate to the Tableau Server URL. This step prevents any active sessions or cookies from being brought back in during the Kerberos authentication process.
  4. Launch Tableau Desktop and sign into Tableau Server.
  5. Open a new connection to the data source.
  6. Publish this data connection or workbook to Tableau Server, and confirm that 'Viewer Credentials' is now an Authentication option.

Cause

This behavior is related to a known issue (ID: 922900) which has been fixed in a recent release of Tableau Desktop. 

Additional Information

Before attempting resolution, confirm that the Tableau Server environment and database have been successfully configured for Kerberos. For more information, see Configure Kerberos

 
Discuss this article... Feedback Forum
Did this article resolve the issue?