For a Server configured for SAML step 3 should launch a browser window which lets you authenticate to your SAML Identity Provider. If successful the browser window should go away and you should then see step 4.
Its a bit hard to debug without knowing what your Identity Provider is and how it is configured. Given the complexity there, your quickest resolution may be talking to Support directly.
If you like you could also post some screenshots of the experience you're seeing here and that may shed a little more light.
Thanks for the response. We are using a custom SAML code base.
I am able to authenticate but the browser doesn't go away, the user experience is the same as if I opened a browser myself and navigated to the application.
It is good to know that this is support and I will open a case with support to find the underlying issue.
Thanks. We do try to test multiple SAML configurations but it may be something specific to your enviornment. Please do follow up with support.
Support came back quickly with the following advice. For some custom SAML applications you must configure Tableau Server to allow Trusted Authentication using the following comand.
tabadmin set wgserver.authentication.desktop_nosaml true
I am facing the same issue and the idp we are using is oif(Oracle) .please suggest what are the steps to be followed
Hi. I encountered the exact same issue and this fix worked perfectly. When signing into a SAML-enabled server via Desktop, once you apply "tabadmin set wgserver.authentication.desktop_nosaml true", Desktop users will NOT be prompted to SAML into the server -- they will sign in as if SAML is not enabled. To recap, here are the steps I followed:
- On your primary server, open command prompt
- Go to bin directory
- Run command "tabadmin set wgserver.authentication.desktop_nosaml true"
- Run command "tabadmin config" (to make sure configuration files are applied to all servers in cluster)
- Run command "tabadmin restart" (to restart Tableau Server)