Customers may experience a partial authentication failure when using the Tableau Lightning Web Component with seamless authentication in Salesforce. In environments where users authenticate to Tableau via UPN (User Principal Name) — common in Microsoft Entra-federated setups — the LWC's default field mapping may pass the user's email address instead of their UPN. When a user's email address and UPN are the same, authentication succeeds. When they differ, that user cannot access Tableau content through the LWC.
This produces a situation where some users see Tableau content normally while others receive authentication errors or a blank view, with no apparent pattern from the end user's perspective. The issue is environmental and configuration-based, not a product defect.
Key conditions:
- Tableau is embedded via the standard Tableau Pulse Lightning Web Component
- UPN and email address are not identical for all users in the IdP
1. Have the Salesforce Admin identify the Salesforce user record field that contains the value matching each user's Tableau username. In UPN-based setups, this is typically a dedicated UPN field on the User object — confirm with the IdP/directory team which field holds the exact string Tableau expects.
2. In Salesforce, navigate to the page or app builder where the Tableau Pulse LWC is configured.
3. Open the LWC component properties. Locate the field used for username mapping passed to Tableau for seamless auth. Change this to the field identified in step 1 (e.g., a custom UPN field rather than the standard Email field).
4. Save the configuration. Test with a user whose UPN and email address differ — they should now authenticate and see Tableau content successfully.
5. If a custom UPN field does not yet exist on the Salesforce User object, work with the Salesforce admin to create one and populate it via the IdP sync or user provisioning process before remapping.
Configure Seamless Authentication for Tableau Pulse in Salesforce LWC
https://help.tableau.com/current/online/en-us/lwc_seamless_auth.htm
005386014

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.