To create an identity, you specify a username and a password. To enable this scenario, you must first create an identity for each user. When users sign-in and enter their credentials, either through Tableau Desktop, tabcmd, API, or web client, Tableau Server verifies the credentials. If the server is configured to use local authentication, then Tableau Server authenticates users. * SSPI is not compatible with the Workspace ONE version of the Tableau Mobile app. Blank cells indicate incompatible authentication sets. Cells marked with an "X" indicate a compatible authentication set. The following table shows authentication methods that can be combined.
Some authentication methods can be used together.
Such access requires additional configuration of the data source on Tableau Server or authentication at the data source when the user connects from Tableau Desktop. In other words, in the default configuration, Tableau Server does not act as a proxy to external data sources. Note: In the context of authentication, it’s important to understand that users are not authorized to access external data sources through Tableau Server by virtue of having an account on the server. For more information about administrators, site roles, groups, Guest User, and user-related administrative tasks, see Users and Site Roles for Users. Site roles define which users are administrators, and which users are content consumers and publishers on the server. For more information see Identity Store.Īs shown in the following table, the type of identity store you implement, in part, will determine your authentication options.Īccess and management permissions are implemented through site roles. Alternatively, if you are not running an LDAP directory, you can use the Tableau Server local identity store. Tableau Server supports arbitrary LDAP directories, but it's been optimized for Active Directory LDAP implementation. There are two, mutually exclusive, identity store options: LDAP and local. Looking for Tableau Server on Linux? See Authentication (Link opens in a new window).Īlthough all user identities are ultimately represented and stored in the Tableau Server repository, you must manage user accounts for Tableau Server in an identity store. The repository manages authorization meta data for user identities. In all cases, whether authentication takes place locally or is external, each user identity must be represented in the Tableau Server repository. In the latter case, you must configure Tableau Server for external authentication technologies such as Kerberos, SSPI, SAML, or OpenID. The method of authentication may be performed by Tableau Server (“local authentication”), or authentication may be performed by an external process. Everyone who needs to access Tableau Server-whether to manage the server, or to publish, browse, or administer content-must be represented as a user in the Tableau Server repository. Authentication verifies a user's identity.
0 kommentar(er)
