Trusted Ticketsis an authentication method in Tableau Server for embedding views in external applications (e.g., portals) without requiring users to log in manually. Here’s how it works:
A trusted application (e.g., a web server) authenticates with Tableau Server using a trusted IP or username/password.
Tableau Server issues a temporary ticket (a unique string).
The ticket is embedded in a view URL (e.g., /trusted//views/...), granting access to the view for a short period (configurable, default 5 minutes).
Option A (Access embedded views without being prompted for credentials): Correct. Trusted tickets enable SSO-like behavior for embedded content, bypassing the login prompt if the ticket is valid. This is ideal for seamless integration into external systems.
Option B (Encrypt database connections): Incorrect. Encryption is handled by data source configurations (e.g., SSL), not trusted tickets, which focus on user authentication.
Option C (Save and edit workbooks): Incorrect. Trusted tickets grant view access, not edit permissions—those depend on the user’s site role and permissions.
Option D (Embed database credentials): Incorrect. Trusted tickets authenticate users to Tableau Server, not databases—database credentials are managed separately in the data source.
Why This Matters: Trusted tickets simplify embedding Tableau content securely in custom applications, enhancing user experience.
[Reference: Tableau Server Documentation - "Trusted Authentication" (https://help.tableau.com/current/server/en-us/trusted_auth.htm)., ]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit