Good day Emmanuel.
The two ways I'm aware of to keep this from happening:
- Enable Guest access for the embedded workbook. Guest access will allow the embedded workbook to display without the login step. This is ideal if the web page is intended to be public, less ideal otherwise.
- If you want or need users to log to your embedded website, have Tableau server and your web page use something like a single signon system, for example Shibboleth or Cosign. Then the credentials will be active when they see the page, and the embedded page authenticated without another login.
Does this help?
thanks for your reply.
Unfortunately neither solutions fit our needs.
As you mentioned, the guest access is by far too open for us.
The second solution is what we currently have. When people click on the Tableau button, they get logged in automatically and the graph is getting displayed (they do not have to login again). But surprisingly, Tableau doesn’t detect the users are logged in before clicking on the button…
Do you know if there is some cookie that could be shared between the two apps?
Good day Emmanuel.
It really depends on what authentication both the hosting web server where the workbook is embedded and the Tableau server are using. Probably a more reliable way is using trusted authentication. Tableau has a trusted authentication service, which requires some sysadmin setup, but should obviate the need for the second login:
The behavior here is due to Tableau Server not being aware of the SAML cookies from the IdP. Once a login session is initiated from either the identity provider (IdP) or Service Provider (SP), then Tableau Server is able to log the user in without having to manually sign in again with the IdP.
Using trusted authentication for those embedded views will get rid of the sign in button all together for you.