A user can have multiple PATs, which allows for granular monitoring and revocation of access rights. PATs are long-lived, and can be revoked without disabling the Tableau user they are attached to.
#TABLEAU PUBLIC LOGON PASSWORD#
A sign in using a PAT returns the same information as a username and password sign in (a credentials token, site LUID, and user LUID), but without the security risk of exposing hard-coded usernames and passwords, or an interactive login experience. For example, the URI to sign in to a site in the 10ay pod would be: 3.16/auth/signin Make a Sign In Request with a Personal Access TokenĪ Personal Access Token (PAT) validates that a user is allowed to sign in to a site. For Tableau Online, the server address in the URI must contain the pod name, such as 10az, 10ay, or us-east-1. The my-server value in the sign in URI is the base URL for your Tableau Server. The following example shows the URI for a Sign In using a POST request: POST 3.16/auth/signin You must use a PAT, instead of user name and password, to make a REST API sign in request to Tableau Online.
(Tableau Online only) If multi-factor authentication (MFA) is enabled with Tableau authentication, PATs are required.For information about the requirements for using SAML, see SAML Requirements. We strongly recommend PAT sign in because it is more secure.
Even if you are manually signed in to your server through SSO, REST API request authentication requires that you first make a REST sign in request, and then use the credentials token from its response in the header of subsequent requests. SAML single sign on (SSO) authentication does not validate REST API requests.
0 kommentar(er)
