<< Back

Authenticating an External Tableau Server using SAML & AD FS

A client recently came to me with an interesting challenge. They wanted to embed Tableau Server dashboards in Salesforce (nicely demonstration by Ellie Fields) however instead of using Tableau Online they intended to install Tableau Server on an Amazon EC2 server alongside Amazon Redshift. Here’s where it gets difficult, it needed to be a seamless single sign-on (SSO) experience from Salesforce to Tableau using enterprise Active Directory (AD) usernames and passwords.

Clearly the authentication username-password challenge had to be done by active directory in order to keep usernames and passwords consistent, however until Tableau Server 8.1 our only option would have been to explore a custom trusted ticket authentication interface. With the introduction of SAML in Tableau 8.1 and Active Directory Federation Services (AD FS) 2.0 with Windows Server 2008 (as an update) & 2012 authentication could pass seamlessly from the active directory to Salesforce and then onto Tableau.

So how do you go about configuring a Tableau Server, not situated anywhere near your enterprise domain, to work with active directory? Here’s how….


It’s assumed you have a working instance of Tableau Server & Windows active directory. The instructions will be based on Server 2012 however should also carry across into Server 2008 with the AD FS 2.0 update. You’ll need a valid SSL certificate key pair for the AD FS server & Tableau Server, I’ll point you in the right direction when it comes to it. It is also important that usernames configured on your Tableau Server match those on your active directory so if you haven’t created an admin account on Tableau which matches the username of your own or test AD account I’d do that now.

Getting a single AD FS instance up and running

I’m going to assume you don’t have AD FS already installed & configured, if you do you can skim read this section, just make sure you save the FederationMetadata xml at the end.

Server Manager

  • We’re going to start in the top right of Server Manager -> Manage -> Add Roles and Features
  • Follow the wizard to install Active Directory Federation Services (may require server restart)

AD FS requires a certificate to be in place in IIS under the Default Site. If you don’t already have a certificate you’ll need to generate a certificate signing request and submit it to a fully configured enterprise or third party certificate authority (I’d recommend RapidSSL as they have lots of instructions about how to do this). Don’t forget the CN (common name) needs to be the fully qualified domain name of your AD FS server as it’ll be seen by the Tableau Server. e.g. adfs.theinformationlab.co.uk

  • BindingsEdit the IIS Default Site bindings to assign the server certificate to the https protocol
  • Start AD FS Management under Administrative Tools
  • On the first run of AD FS Management you’ll be presented with a wizard to configure the server. The questions are simple, at this point you’re just looking to install a single instance of AD FS, not configure a farm (if you are configuring a farm why are you reading my step by step guide).
  • When the wizard completes you should see a bunch of green ticks. You can then test that all’s well by going to https://yourserver.yourdomain.com/FederationMetadata/2007-06/FederationMetadata.xml
  • Save the FederationMetadata.xml file in a safe place, ideally transfer it now to your Tableau Server.
  • Finally Tableau Server requires forms based authentication to serve logins via a web browser, Tableau Desktop and the Tableau Mobile app. In web.config found in the C:inetpubadfsls directory modify the tag order under <localAuthenticationTypes> so that <add name=”Forms” page=”FormsSignIn.aspx” /> appears first in the list. You can customise the login form by editing FormsSignIn.aspx in the same directory.

Congrats! AD FS is up and running….make yourself a coffee.

Configure Tableau Server for SAML authentication

While these steps are specific to AD FS SAML integration they can be translated to any SAML identity provider (IdP).

  • SSL ConfigIf you don’t already have an SSL certificate for your Tableau Server follow these steps. Again you’ll need to have the request signed by a fully configured enterprise or a third party CA. Don’t forget the CN (common name) needs to be the fully qualified domain name of your Tableau Server as it’ll be seen by the AD FS Server. e.g. tableau.theinformationlab.co.uk
  • Open the Tableau Server configuration window and select the SSL tab.
  • If SSL isn’t already enabled tick the box and assign the certificate and key files created in the previous step
  • Stop the Tableau Server (tabadmin stop), click OK on the configuration box, start the Tableau Server (tabadmin start) and check that the server is fully operational (tabadmin status –verbose) and is now accessed in a web browser via https instead of http
  • SAML ConfigOpen the Tableau configuration window again, this time selecting the SAML tab
  • The Tableau Server return URL is the URL the user will be sent to after authenticating with SAML. It should be the URL of your Tableau Server beginning with https (to comply with AD FS endpoint requirements).
  • You can give the server any SAML entity ID although it must be unique on your AD FS
  • The SAML certificate and key files can be those used by your SSL config or they can be unique. Importantly the CN must match the return URL FQDN
  • Once they’re all set you can export your metadata file, this file needs to be copied across to your AD FS server
  • Remember the FederationMetadata.xml file we saved earlier? Select it as the SAML IdP Metadata file
  • Stop Tableau Server (tabadmin stop), click OK on the config screen, start the Tableau Server (tabadmin start)

While Tableau’s starting go back to your AD FS server with the newly exported Metadata xml file.

Add Tableau to AD FS

  • In AD FS Management, under Trust Relationships, right click on Relying Party Trust and Add Relying Party Trust
  • In the second wizard screen select “Import data about the relying party from a file” and browse to the exported Tableau SAML metadata xml file (the one you most recently copied)
  • Click next…any error alerts at this point need to be rectified, the import should be seamless
  • Give the config a friendly name e g. Tableau SAML and finish off the wizard
  • SAML RulesYou should be asked to create some claim rules. If not right click on your new Relying Party Trust and select Edit Claim Rules.
  • Under the Issuance Transform Rules tab cluck the Add Rule button
  • For SAML authentication Tableau requires two attributes to be returned, Name ID and username, both of which can make use of the same AD attribute SAM-Account-Name
  • Once configured all should be ready to go. Try logging in with a username already authorised on the Tableau Server (don’t forget to use the AD password)


  • Most errors are caused by poorly configured certificates. Make sure your certificates appear valid to both servers (during the FederationMetadata.XML or the Tableau SSL test you shouldn’t receive any browser warnings about your certificates)
  • If the AD FS accepts your login but doesn’t forward you on to Tableau check the AD FS server logs. Some certificates require hash algorithm SHA-1 rather than SHA-256, this is set in the trust partner properties
  • The following log files are useful (that can be found under ProgramData for installations on the C drive, Program Files for all other drives):
    • tabadming.log (TableauTableau Serverlogs) – As the Tableau Server comes back online and “Waiting for wgserver on 8000 to become ready” appears in the log look out for any 404 errors. This would indicate a problem with your certificates
    • error.log (TableauTableau Serverdatatabsvclogshttpd) – Certificate errors referencing localhost:443 are OK however any other certificate errors would indicate a problem
    • wgserver-#.log (TableauTableau Serverdatatabsvclogswgserver) – This is where you’ll find SAML specific errors such as missing claim attributes

If all of that seems too much like hard work…why not get The Information Lab team in? Email us info@theinformationlab.co.uk

Sign IN

Craig Bloodworth

York, UK

14 thoughts on “Authenticating an External Tableau Server using SAML & AD FS

  1. Great info Craig; Saml and idp authentication are one of the key features that are lifting Tableau to enterprise class in 8.1. Information on configuration is a bit sparse on the Web right now, so really useful to see how it is done with ad fs.

  2. This is an excellent article. Is there an advantage of using SAML integration over the previous Tableau ticketing feature?

  3. Wonderful useful information in detail about SAML and AD FS authentication.Definitely this will be key feature to raise heights with tableau 8.1

  4. We have configured the tableau server SAML and ADFS…

    After the configuration , we are not able to log-in to tableau server.

    SAML handshake is happening on the ADFS and tableau..but failed to auth on tableau side. Please assist.

    1. We have configured SAML on Tableau and ADFS as per above instructions. But, still no success. Can you please help us by providing few detailed documentation. Also, I am not getting anything in below log file.

  5. This is a really useful document but will Tableau support ADFS 3.0?

    I have checked all the documentation and that only mentions ADFS 2.0, we have tried setting it up using those settings but these do not appear to work with ADFS 3.0, so was wondering if anybody has implemented Tableau with ADFS 3.0

      1. Just wanted to chime in and say it works fine on ADFS 3.0 following this guide. The one critical piece of advice I have though, ignore the log files mentioned. The Event Logs on both the Tableau server and the ADFS server are the best tools for diagnosing any issues. Sometimes the Tableau errors are not very meaningful, but in that case there will always be a corresponding error on the ADFS side that should make more sense.

        For the SAML cert and key, don’t use the site SSL certificate or you’ll have to update the configuration on ADFS every time you need to renew. Just use openssl on Ubuntu to generate a key file with the passphase stripped out and simply self-sign a certificate with a long enough lifespan that you never have to worry about it again.

        As for ADFS, just remember to set the RP to use SHA-1 as mentioned. I also needed to tweak my claim rules to support users in multiple domains, but if you ADFS and AD servers are on the same domain as all your users, then this guide should just work for you.

        1. multi domain… do you mean by adding in Trusted Claims Providers that reference additional external adfs servers?

          I’ve been able to get this running just fine using our internal ADFS. No issues there. But I need to add another companies ADFS and while I can get the other companies adfs to successfully log them into our internal IDPInitiatedSignon page… I can’t seem to get Tableau to recognize their claims…

  6. Hi,

    I have a use case. I have a PHP admin portal built in Laravel framework. I have a Tableau server hosted on EC2. I want user to visit the admin portal which will take user to Tableau login page(if not logged in to Tableau) and return the response.

    I have few questions, some of them are quite obvious but I just want to confirm it.

    1. In the above mentioned use case admin portal will be SP, right?
    2. In the above mentioned use case Tableau server will be an IDP, right?
    3. Can we use/configure Tableau server as IDP? and How?

    It would be a great help if you answers these question and a bit explanation for question 3.

    Thanks in advance,
    Paresh (kendreparesh@gmail.com)

  7. Configuring this was pretty straight forward and we have it working. The problem is when the session times out users have to clear cache from the browser in order to sign back into a dashboard.
    Anyone solve this yet?

Leave a Reply

Your email address will not be published. Required fields are marked *