In this article we will learn how to:
- Implement single sign on (SSO) for Tableau Online with security assertion markup language (SAML) identity provider (IdP) Okta
- Create a simple embedded analytics application that embeds a Tableau Online dashboard into a web page
- Provide a seamless end user experience in an embedded analytics application (note that this may be at odds with the most robust security setup configuration)
You might also find this article useful:
Tableau Online account. If you do not have a Tableau Online account, please let us know and we will spin up a trial for you or help you make a purchase.
- Admin access to your Tableau Online account.
- Tableau dashboard content published you want to use for embedded analytics. For testing, you can use any Tableau dashboard published to Tableau Online.
- Okta account. If you do not have an account with Okta, you can sign up for a free trial here.
- You'll need admin access to your Okta account.
Web Server for Embedded Analytics Application
We followed the set up instructions directly from Okta's help documentation: How to Configure SAML 2.0 for Tableau Server
Tableau also has it's own set of instructions as an alternative or for more information: Configure SAML with Okta
As part of our testing, we wanted to make sure the embedded analytics experience was as seamless as possible.
DO THIS AT YOUR OWN RISK. Tableau warns about this in their documentation and in Tableau Online itself.
Tableau Online Additional Settings
On the Tableau Online side, under Settings -> Authentication -> Authentication types:
Under section "6 Embedding options", click "Authenticate using an inline frame (less secure; not supported by all IdPs)".
Okta Additional Settings
In the Okta app, under Admin -> Settings -> Customization and under the IFrame Embedding section, we checked to "Allow IFrame embedding".
As a last step, update the authentication of any existing/new Tableau Online users you want to authenticate via Okta. Make sure they are using okta.com (SAML) as their authentication rather than Tableau.
Note that a user can only authenticate via a single method, either Okta or Tableau.
Update the Authentication of Existing Tableau Online Users
On the Tableau Online users page, select the user and click the three dots (...).
Change the Authentication from Tableau to okta.com (SAML) and click update.
If you are testing this on your own user, this will log you out of Tableau Online. When you log back in you will authenticate via Okta.
The user should now have okta.com (SAML) in the Authentication column.
Add New Users to Tableau Online and Have Them Authenticate Via Okta
When adding new users to your Tableau Online site, click the "+ Add Users" orange button:
If you have one or a few users, click "Enter Email Addresses". You can also import using a CSV file if you have a large list.
Make sure that you select "Add users for okta.com (SAML) authentication".
Embed a Tableau Dashboard in a Website
Now that you have at least have one user in Tableau Online authenticating via Okta, it is time to test the end user experience in an embedded analytics environment.
For this part, you will need a simple HTML page hosted by a web server. Check out our blog here for instructions on setting up a simple web server with Python and embedding a Tableau dashboard.
Simply navigate to a Tableau dashboard in your Tableau Online and click the "Share" button.
There are several ways to embed a Tableau dashboard, in this case, just click "Embed Code" to copy the code.
On your HTML page, paste the "Embed Code".
Here's a simple example of the HTML:
Save and refresh your page.
If you are still logged into Tableau Online, this is what you will see:
SSO and End-User Experience
Now let's test the embedded analytics application from the end user's perspective. In an external, customer facing embedded analytics application, your end users will probably not be aware that Tableau is driving their analytics experience nor will they be aware that your application is using Okta for authentication. All they will see is your application's login screen.
So let's mimic that environment.
Sign out of Okta.
Sign out of Tableau Online. It turns out that this step is harder than it seems. There is no sign out button in Tableau Online when using Okta for authentication. So, I needed to do the following:
- Change my user's authentication method back to Tableau.
- Sign back in using my Tableau Online credentials.
- Change my user's authentication method to okta.com (SAML). This logs the user out again.
Sign back into Okta.
Refresh your embedded analytics application's page and you should see this:
If your user clicks "Sign in to Tableau Online", their experience will be something like this:
The end user only has to go through this "login" flow once or until they are signed out of Tableau Online. Tableau Online's idle session timeout duration is 2 hours (and cannot be modified).
The end user experience is less than ideal with a user needing to click a button to authenticate, however, they do not have to log in with a username and password. If you are looking for a more seamless embedded analytics experience for your end users, we have products that solve this.
Take advantage of everything Zuar offers to companies using Tableau!
- Rapid Portals are an easy way to provide branded Tableau dashboards. Monetize your data or provide secure access outside of corporate firewalls.
- Transport, warehouse, transform, model, report & monitor. Mitto gets data flowing from hundreds of potential sources into a single destination for Tableau.
- Zuar's team of Tableau-certified consultants can take the headaches out of even the most complex projects.
- Read our other articles Tableau-focused articles.