Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://help.tableau.com/current/server-linux/en-us/connected_apps_eas.htm below:

Configure Connected Apps with OAuth 2.0 Trust

As a Tableau Server admin, you can register one or more external authorization servers (EASs) to establish a trust relationship between your Tableau Server and the EAS using the OAuth 2.0 standard protocol.

Important:

• Some of the procedures in this topic require configuration with third party software and services. We’ve made a best effort to verify the procedures to enable the EAS feature on Tableau Server. However, third-party software and services might change or your organization might differ. If you encounter issues, refer to your third-party documentation for authoritative configuration details and support.
• To enable embedding through EAS, Tableau Server must be configured to use SSL for HTTP traffic.
• In order for the session token to be valid, the clocks of the external application and the server that hosts the external application must be set to Coordinated Universal Time (UTC). If either clock uses a different standard, the connected app will not be trusted.

The trust relationship between your Tableau Server site and external application is established and verified through an authentication token in the JSON Web Token (JWT) standard.

When embedded Tableau content is loaded in your external application, Authorization Code Flow, OAuth flow is used. After users successfully sign in to the IdP, they are then automatically signed in to Tableau Server. Follow the steps described below to register your EAS with Tableau Server .

The following components of the connected work together with the JWT in your external application to authenticate users and display embedded content.

• External authorization server (EAS): The server, typically your IdP, that functions as the interface between the user and the external application. The server authenticates and authorizes user access to the protected Tableau content.

• Issuer URL: The URL that uniquely identifies the EAS instance.

The diagram below illustrates how authentication works between your external authorization server (EAS), external application (web server and webpage), and Tableau connected app.

1. User visits the webpage: When a user visits the embedded content on a webpage, the webpage sends a GET request to the external application.

2. External application redirects request to EAS: External application responds with a webpage that redirects to the external authorization server (EAS).

3. User authenticates with EAS: User authenticates and authorizes with the EAS.

4. EAS responds to webpage with authorization code: The EAS responds to the page with an authorization code and redirects back to the webpage.

5. EAS converts authorization code to JWT: Webpage calls the EAS to convert the authorization code to a JWT, which the webpage puts into the embedded content’s URL.

6. Webpage requests content from Tableau: Webpage loads the iFrame and sends a GET request to Tableau.

7. Tableau validates the token: Tableau validates the JWT in the URL with the signature and responds with the content and respects the embedding scopes defined in the JWT.

To register an EAS with Tableau Server , you must have an EAS already configured. In addition, the EAS must send a valid JSON Web Token (JWT) that contains the registered claims and header listed in the table below.

Value must be: "tableau"

For embedding workflows, supported values include:

"tableau:views:embed"
"tableau:views:embed_authoring" (Added in Tableau Server 2022.3)
"tableau:metrics:embed" ( Retired in Tableau Server 2023.3 )
"tableau:ask_data:embed"( Added in Tableau Server 2023.1. Will be retired in Tableau Server 2024.2)

Notes:

• Values must be passed as a list type.
• For tableau:views:embed, the scope respects users’ permissions already configured in Tableau Server and allows users to interact with the tools in the embedded view if available in the original view.
• We recommend the embed code exclude the toolbar parameter. For more information see Known issues (embedding workflows only) below.

For REST API authorization workflows, see REST API methods that support JWT authorization.

For Metadata API workflows that use the REST API for authentication, the only supported scope is tableau:content:read.

Value must match the name of one or more groups in Tableau Server. For more information, see Dynamic group membership (embedding workflows only) section below.

For embedding workflows only.

Starting in Tableau Server 2025.1, you can include user attributes in the JWT. Then when user attribute functions are used in embedded content, Tableau checks the authenticated user’s context and determines what data can display at runtime.

Notes:

• Check the Tableau Embedding API v3(Link opens in a new window) Help for known issues and limitations that might affect your workflow.

• For the user attribute to work, 1) you must enable the user attribute capability through the Update Embedding Settings for a Site(Link opens in a new window) method using Tableau REST API and optionally enable the features.VizDataServiceClientEnable(Link opens in a new window) TSM option, and 2) the content author must create a user attribute function(Link opens in a new window).
• User attributes are case sensitive.

Note: The JWT claims above are documented in the Registered Claim Names(Link opens in a new window) section in the documentation distributed by the Internet Engineering Task Force (IETF) organization.

By registering your EAS with Tableau Server, you establish a trust relationship between the EAS and Tableau Server. This means when users access Tableau content embedded in your external application, they are redirected to authenticate with the IdP. The EAS generates the authentication token, which is passed to Tableau Server for verification. After the trust relationship is verified, access to the embedded content is granted users.

Note: Some EAS support the option to display a consent dialog that asks for users’ approval for the application to access Tableau content. To ensure the best experience for your users, we recommend you configure your EAS to automatically consent to the external application’s request on users’ behalf.

Beginning in Tableau Server 2024.2, you can configure site-level EAS. To register an EAS at the site-level, connected apps must be enabled in Tableau Server Manager (TSM).

There are two ways you can register server-wide EAS: using the TSM web UI or using TSM CLI.

After registering the EAS, the established trust relationship applies to all sites on Tableau Server.

1. As a Tableau Server admin, sign in to the Tableau Services Manager (TSM) web UI. For more information, see Sign in to Tableau Services Manager Web UI.

2. Do one of the following:

   • In Tableau Server 2024.2 and later, navigate to User Identity & Access page > Connected Apps tab.

   • In Tableau Server 2023.3 and earlier, navigate to User Identity & Access page > Authorization Server tab.

3. Do one of the following:

   • In Tableau Server 2024.2 and later:

     1. Select the Enable connected apps check box.

     2. Select the second radio button, Allow connected apps (configure at site level) and server-wide OAuth 2.0 trust (configure below).

     3. In the Issuer URL text box, paste the issuer URL of the EAS.

     4. Click the Save Pending Changes button.

   • In Tableau Server 2023.3 and earlier:

     1. Select the Enable OAuth access for embedded content check box.

     2. In the Issuer URL text box, paste the issuer URL of the EAS.

     3. Click the Save Pending Changes button.

4. When finished, do the following:

   1. In the upper-right corner of the page, click the Pending Changes button.

   2. In the bottom-right corner of the page, click the Apply Changes and Restart button to stop and restart Tableau Server.

1. Open a command prompt as an admin on the initial node (where TSM is installed) in the cluster.

2. Run the following commands:

   tsm configuration set -k vizportal.oauth.external_authorization.enabled -v true
   tsm configuration set -k vizportal.oauth.external_authorization_server.issuer -v "<issuer_url_of_EAS>"
   tsm restart

Beginning in Tableau Server 2024.2, you can register one or more EASs for a site. After registering the EAS at the site level, the established trust relationship applies to the site only.

Note: A prerequisite to configuring site-level EAS is that connected apps is enabled in TSM.

1. As a Tableau Server admin, sign in to the Tableau Services Manager (TSM) web UI. For more information, see Sign in to Tableau Services Manager Web UI.

2. Navigate to User Identity & Access page > Connected Apps tab.

3. Select the Enable connected apps check box.

4. Do one of the following:

   • Select the first radio button, Allow connected apps (configure at site level) to enable registering EASs at the site-level only.

   • (Default) Select the second radio button, Allow connected apps (configure at site level) and server-wide OAuth 2.0 trust (configure below) to enable registering EASs at both the site-level and server-wide. If you choose this option, ensure the issuer URL specified at the site-level is different from the server-wide issuer URL.

5. Click the Save Pending Changes button.

6. When finished, do the following:

   1. In the upper-right corner of the page, click the Pending Changes button.

   2. In the bottom-right corner of the page, click the Apply Changes and Restart button to stop and restart Tableau Server.

1. As a Tableau Server admin, sign in to Tableau Server.

2. From the left pane, select Settings > Connected Apps.

3. Click the New Connected App button drop-down arrow and select OAuth 2.0 Trust.

4. In the Create Connected App dialog box, do the following:
   

   1. In the Name text box, enter a name for the connected app.

   2. In the Issuer URL text box, paste the issuer URL of the EAS.

   3. Select the Enable connected app. For security purposes, a connected app is set to disabled by default when created.

   4. When finished, click the Create button.

5. After the connected app is created, copy the connected app’s site ID. The site ID is used for the JWT's "aud" (Audience) claim described in Step 1 above.

After configuring Tableau Server to use your EAS, you must add embed code to your external application. Ensure that you include the valid JWT generated by your EAS, as described in Step 1, in the web component that your external application calls.

For more information about embedding Tableau content, see one or both of the following:

• Embed metrics, see Embed Metrics into Webpages(Link opens in a new window) topic in the Tableau Help. (In Tableau Server 2023.3 , Tableau retired the ability to embed metrics.)
• Embed Tableau views and metrics using the Tableau Embedding API v3(Link opens in a new window).

Note: For users to successfully authenticate when they access embedded content, browsers must be configured to allow third-party cookies.

Starting in Tableau Server 2023.3 , you and your users can control whether Tableau content can be embedded without restriction or restricted to certain domains using the Update Embedding Settings for Site method in Tableau REST API.

By default, the unrestrictedEmbedding site setting for embedding is set to true to allow unrestricted embedding. Alternatively, you and your users can set the setting to false and specify the domains where Tableau content in external applications can be embedded using the allowList parameter.

For more information, see one or both of the following:

• Update Embedding Settings for Site(Link opens in a new window) in the Tableau REST API Help
• Tableau Site Setting for Embedding(Link opens in a new window) in the Tableau Embedding API v3 Help.

After the JWT has been configured, you must add the valid JWT to the REST API Sign In request for authorized access. For more information, see Access Scopes for Connected Apps.

After the JWT has been configured, you must add the valid JWT to the REST API Sign In request. For more information, see Access Scopes for Connected Apps.

Beginning in Tableau Server 2024.2 , if connected apps are configured and the capability’s setting is enabled, you can dynamically control group membership through custom claims included in the JWT sent by the external application.

When configured, during user authentication, the external application sends the JWT that contains two custom claims for group membership: group (https://tableau.com/groups) and group names (for example, "Group1" and "Group2") to assert the user into. Tableau validates the JWT and then enables access to the groups and the content whose permissions are dependent on those groups.

For more information, see Dynamic group membership using assertions.

There are a couple of known issues when using connected apps that will be addressed in a future release.

• Toolbar features: When embedded content has the toolbar parameter defined, not all toolbar features will work. To work around this issue, we recommend you hide the toolbar parameter like in the example below.

  <tableau-viz id='tab-viz' src='https://<your_server>/t/<your_site>/...'
  	toolbar='hidden'>
  </tableau-viz>

• Published data sources: Published data sources set to Prompt User for database credentials will not display. To work around this issue, if possible, we recommend data source owners embed their database credentials instead.

• Embedded views on multiple sites: In Tableau Server 2023.1 and earlier, switching between views on different sites in the same browser causes error 1008: Could not fetch secret for connect app. To work around this issue, upgrade to Tableau Server 2023.3 or later.

When embedded content fails to display in your external application or Tableau REST API authorization fails, you can use a browser’s developer tools to inspect and identify error codes that might be associated with the EAS feature enabled on Tableau Server .

Refer to the table below to review the description of the error code and potential resolution.

• The 'exp' (Expiration Time) exceeds the default maximum validity period. To resolve this issue, review registered claims(Link opens in a new window) required for a valid JWT and ensure the correct value is used. To change the maximum validity period, you can use the vizportal.oauth.external_authorization_server.max_expiration_period_in_minutes command.
• The 'sub' (Subject) is calling an unknown user. To resolve this issue, verify the 'sub' claim is "username". This value is case sensitive.

• The 'aud' (Audience) value referenced in the JWT uses the "tableau" value. This value is case sensitive.
• The 'aud' (Audience) and 'sub' (Subject) are included in the JWT.

To resolve this issue, verify the correct issuer is being called. To change the issuer URL, you can use the vizportal.oauth.external_authorization_server.issuer command.

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