Duo Access Gateway will reach end of life in October 2023. Customers may not create new DAG applications after May 19, 2022. Please see the Guide to Duo Access Gateway end of life for more details.
Use the Duo Single Sign-on Generic Service Provider application to protect Tableau with Duo Single Sign-On, our cloud-hosted identity provider featuring Duo Central and the Duo Universal Prompt.
If you already use Duo Access Gateway to protect Tableau, try the DAG to Duo SSO application migration process.
This documentation is for Tableau Online only. For information about Tableau Server, see the Duo Protection for Tableau with Duo Access Gateway documentation.
As business applications move from on-premises to cloud hosted solutions, users experience password fatigue due to disparate logons for different applications. Single sign-on (SSO) technologies seek to unify identities across systems and reduce the number of different credentials a user has to remember or input to gain access to resources.
While SSO is convenient for users, it presents new security challenges. If a user's primary password is compromised, attackers may be able to gain access to multiple resources. In addition, as sensitive information makes its way to cloud-hosted services it is even more important to secure access by implementing two-factor authentication and zero-trust policies.
Duo Access Gateway (DAG), our on-premises SSO product, layers Duo's strong authentication and flexible policy engine on top of Tableau logins using the Security Assertion Markup Language (SAML) 2.0 authentication standard. Duo Access Gateway acts as an identity provider (IdP), authenticating your users using existing on-premises or cloud-based directory credentials and prompting for two-factor authentication before permitting access to Tableau.
Duo Access Gateway is included in the Duo Beyond, Duo Access, and Duo MFA plans, which also include the ability to define policies that enforce unique controls for each individual SSO application. For example, you can require that Salesforce users complete two-factor authentication at every login, but only once every seven days when accessing Tableau. Duo checks the user, device, and network against an application's policy before allowing access to the application.
Install Duo Access Gateway on a server in your DMZ. Follow our instructions for deploying the server, configuring DAG settings, and adding an Authentication Source.
Add the attributes from the table below that correspond to the Duo attributes Mail attribute, Last name attribute, and First name attribute in the "Attributes" field when configuring your Active Directory or OpenLDAP authentication source in the DAG admin console, separated by a comma. For example, if Active Directory is your authentication source, enter mail,sn,givenName in the "Attributes" field.
|Duo Attribute||Active Directory||OpenLDAP|
|First name attribute||givenName||gn|
|Last name attribute||sn||sn|
If your organization uses other directory attributes than the ones listed here then enter those attribute names instead. If you've already configured the attributes list for another cloud service provider, append the additional attributes not already present to the list, separated by a comma.
After completing the initial DAG configuration steps, click Applications on the left side of the Duo Access Gateway admin console.
Scroll down the Applications page to the Metadata section. This is the information you need to provide to Datadog when configuring SSO. Click the Download XML metadata link to obtain the DAG metadata file (the downloaded file is named "dag.xml").
Add the Duo Access Gateway as a new single sign-on provider for Tableau Online.
Log into your Tableau Online account as an administrative user.
Click Settings at the top of the Tableau Online page. Once on the "Settings" page click the Authentication tab.
Under "Authentication Types" check the box next to Single sign-on with SAML. New options will appear.
In "1 Export metadata from Tableau Online" locate the Tableau Online entity ID. Copy the information after "alias="; you will need this later.
Example: If the Entity ID is https://sso.online.tableau.com/public/sp/metadata?alias=12ab3456-89b4-4444-8956-0b0ccb870954 you will want to copy 12ab3456-89b4-4444-8956-0b0ccb870954.
In "4 Import metadata file into Tableau Online" click Browse.. next to IdP metadata file. Select the dag.xml file you downloaded earlier and then click Apply. Information will be automatically loaded into the next two fields.
In "5 Match attributes" fill out the fields with information from the table below:
|Tableau Field||IdP Field|
|Display Name: First name||User.FirstName|
|Display Name: Last name||User.LastName|
Click Apply once you've filled out all the required fields.
Scroll down on the page and set "Default authentication type for embedded views" to Single sign-on with SAML.
Learn more about Tableau Online SSO at the Tableau Online Help.
Log on to the Duo Admin Panel and navigate to Applications.
Click Protect an Application and locate the entry for Tableau Online with a protection type of "2FA with SSO self-hosted (Duo Access Gateway)" in the applications list. Click Protect to the far-right to start configuring Tableau Online. See Protecting Applications for more information about protecting applications in Duo and additional application options.
The Alias is the Tableau Online Entity ID alias value you made note of earlier.
Tableau Online uses the Mail attribute, First name attribute, and Last name attribute when authenticating. We've mapped those to DAG supported authentication source attributes as follows:
|Duo Attribute||Active Directory||OpenLDAP||SAML IdP||Azure|
|First name attribute||givenName||gn||givenName||given_name||givenName|
|Last name attribute||sn||sn||sn||family_name||surname|
If you are using non-standard attributes for your authentication source, check the Custom attributes box and enter the names of the attributes you wish to use instead.
Click Save Configuration when done.
You can adjust additional settings for your new SAML application at this time — like changing the application's name from the default value, enabling self-service, or assigning a group policy — or come back and change the application's policies and settings after you finish SSO setup. If you do update any settings, click the Save Changes button when done.
Click the Download your configuration file link to obtain the Tableau application settings (as a JSON file).
Before you do this, verify that you updated the "Attributes" list for your Duo Access Gateway authentication source as specified here.
Return to the Applications page of the DAG admin console session.
Click the Choose File button in the "Add Application" section of the page and locate the Tableau Online SAML application JSON file you downloaded from the Duo Admin Panel earlier. Click the Upload button after selecting the JSON configuration file.
The Tableau Online SAML application is added.
Tableau Online requires you to enable to SAML on a per-user basis.
Click Users at the top of the Tableau Online page. Click the ... button next to the user you want to sign in with SSO. Select Authentication... from the drop-down. A new window will appear.
On the "Authentication" pop-up select SAML. The page will save and close automatically.
Click Users at the top of the Tableau Online page. Click the + Add Users button and select "Enter Email Addresses" or "Import From File". A new window will appear.
Select the option Add users for single sign-on authentication (SAML) at the top of the screen and continue adding users as you normally would.
If your organization enabled the Duo Access Gateway portal, log into the portal page using the link provided by your administrator. Click Tableau Online from the dashboard to access the application.
You can also access Tableau Online by going to the Tableau Online login page, entering your e-mail address, and clicking Sign In. This redirects to the Duo Access Gateway login page. Enter your Authentication Source logon information, approve Duo two-factor authentication, and get redirected back to the Tableau site after authenticating.
Congratulations! Your Tableau users now authenticate using Duo Access Gateway.
If you plan to permit use of WebAuthn authentication methods (security keys, U2F tokens, or Touch ID) in the traditional Duo Prompt, Duo recommends configuring allowed hostnames for this application and any others that show the inline Duo Prompt before onboarding your end-users.
The Duo Universal Prompt has built-in protection from unauthorized domains so this setting does not apply.
Microsoft's Active Directory Federation Services (AD FS) is a popular choice for SSO because it easily integrates with the AD identity store many organizations already have deployed. Duo's support for cloud applications and SSO drops in to an existing AD FS installation to provide secondary authentication after a user passes primary authentication (successful Active Directory logon).
If you don't already have AD federation running the first step is to install and configure Microsoft AD FS in your organization. Deployment Guides for AD FS versions 2.1, and 3.0/4.0 are available from Microsoft.
Once your AD FS services are up and running, the second step is to configure the SSO partnership between your AD FS service and the external cloud resource, in this case Tableau. Learn more about configuring Tableau SSO with AD FS at the Tableau Online Help site.
After you have successfully configured and tested AD FS SSO login to Tableau using your AD domain credentials, you can then install the Duo AD FS integration. AD FS protection is included with Duo's paid plans.
With the Duo integration for AD FS installed, users pass primary authentication to the AD FS service as usual. Once primary authentication succeeds, users are forwarded to the Duo service for secondary authentication. After approving logon using one of Duo's authentication methods, the user is fully logged in to Tableau.
Using a third-party SSO provider for cloud application access? Duo partners with leading cloud SSO providers like Okta and OneLogin to secure access with our strong and flexible authentication platform.