After youâve added trusted IP addresses to Tableau Server, youâre ready to configure your web server to get tickets from Tableau Server via POST requests (Step 2 in the diagram). The POST request must be sent to http://<server_name>/trusted. For example, the POSTÂ request must be sent to http://tabserv/trusted not http://tabserv.
Note: If SSLÂ is enabled you must use https instead of http. For example:Â https://tabserv/trusted.
Hereâs the data you can use in a POST request to Tableau Server:
username=<username> (required): The username for a licensed Tableau Server user. If you are using Local Authentication the username can be a simple string (for example, username=jsmith). If you are using Active Directory with multiple domains you must include the domain name with the user name (for example, username=MyCo\jsmith).
target_site=<site id> (required if view not on Default site): Specifies the site containing the view if Tableau Server is running multiple sites and the view is on a site other than the Default site (for example, target_site=Sales). The value you use for <site id> should be the Site ID that was provided when the site was created. This value is case sensitive. If the Site ID is SAles, then the target_site=SAles.
client_ip=<IP address> (optional): Used to specifiy the IP address of the computer whose web browser is accessing the view (for example, client_ip=123.45.67.891). It is not the IP address of the web server making the POST request of Tableau Server. If you decide to use this parameter, see Optional: Configure Client IP Matching for more information.
Tableau Serverâs response to the POST request will be a unique string (the ticket). If Tableau Server isnât able to process the request, the return will be -1. See Ticket Value of -1 Returned from Tableau Server for tips on how to correct this. Also, in order for users to successfully authenticate when they click an embedded view, their browsers must be configured to allow third-party cookies.
The ticket format changed in Tableau Server 10.2. The ticket format is now a string composed of two parts. Each part is a 128 bit string that is encoded before it is returned to the client. The first part is a universally unique ID (UUID v4) that is Base64-encoded. The second part is a 24-character secure random string. The concatenation of these parts can be expressed as Base64(UUIDv4):SecureRandomString. An example of a ticket might look like this: 9D1ObyqDQmSIOyQpKdy4Sw==:dg62gCsSE0QRArXNTOp6mlJ5.
Next, you need to add code that allows the web server to construct an URL for the view that includes the viewâs location and the ticket.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4