Please enable JavaScript.

Coggle requires JavaScript to display documents.

Authentication Options (Tableau Online Authentication (SAML (Caveats…

- - - - e.g. active directory!
    - - Advise to have at least one server admin who is authenticated by TableauID, so you will still have access to server is SAML or IdP is down
      - cannot support SAML and Kerberos together
- - - - authentication managed by Identity Store of Tableau Server
      - use this if...(1) not using (and don't want to use AD and (2) if wanting to enable openID for SSO
      - Cannot set password policies or account lockouts on failed authentication attempts
    - - AD
        
        credentials managed and verified by AD
        
        Tableau Server wil sync users and groups from AD to the identity store
        
        site and server roles need to be assigned once users are in Tableau Serer
  - - - external identity provider authenticates the user's credentials (AD or local auth.)
    - - if Kerberos is enabled in environment and server is configured to use AD authentication
    - - lets users sign in to an identity provider such as Google (only with local auth.)
    - - sets up a trusted relationship between Tableau Server and 1+ web servers. This means that when Tableau Server receives a request from a trusted web server, it assumes the web server has already handeled the authentication that is necessary
    - - if Tableau Server is configured with AD, then you can enabe automatic logon (similar to SSO)
- - - - functionality is specific to Tableau Server
      - Configuration: configure Tableau Server to trust an ip address, which will ten be allowed to authenticate users
      - POST request: When the user goes to embedded views on web app, the web application will make a server-side POST request to Tableau Server passing in the users’s Tableau Server username, the site the content exists on, and, optionally, the client’s ip address in the form data. If the ip address making the request is trusted, and the user exists in Tableau Server, Tableau Server will return a ticket.
      - Client experience: Client loads the view with the ticket: Your web application now instructs the client to load the url of the desired resource, with the ticket inserted. If the ticket is valid, Tableau Server will start a session for the user and the user will see the visualization. Of course, the user does not see the HTTP requests going on behind the scenes, but simply loads a page in your application and sees embedded Tableau content without having to signin.