Deployment setup

With a multi-cloud setup, you can deploy to Qlik Sense Enterprise SaaS. Qlik Sense Enterprise SaaS supports deployment on an infrastructure managed by Qlik.

The setup differs depending on whether or not you use a local bearer token.

Setup with a local bearer token

A local bearer token simplifies the deployment setup. Instead of using the token endpoint, client ID, and client secret properties to retrieve a bearer token from the IdP, a bearer token is generated locally.

Before you start setting up your deployment, make sure you have the tenant URL, provided by Qlik in your welcome email.

To set up your deployment:

1. In the bottom left corner, click Set up new.

2. Enter a deployment name.

3. API endpoint: Enter the tenant URL, which is sent to you from Qlik.

4. Enter audience: qlik.api. Audience is needed by the app distribution service to get API tokens from cloud.

5. Ensure that Use local bearer token is selected and click Apply.

   The local bearer token is generated.

6. By default, the Qlik Cloud format check box is selected. The text box then displays the IdP definition.

7. Choose the format you want to use and click Copy to clipboard to save the text. You need this text when you configure your tenant.

8. For Qlik Sense Enterprise SaaS, you paste the IdP definition in the Local bearer token text box on the tenant configuration page.

Setup with IdP integration

Before you start setting up your deployment, make sure you have the following:

• Client ID and client secret (collected from your IdP provider)

• Token endpoint

• Tenant URL (provided by Qlik in your welcome email)

To set up your deployment:

1. In the bottom left corner, click Set up new.

2. Enter a deployment name. (You can use this name in distribution policies for the distribution of apps.)

3. API endpoint: Enter the tenant URL, which is sent to you from Qlik.

4. Enter audience: qlik.api. Audience is needed by the app distribution service to get API tokens from cloud.

5. Enter Client ID and Client secret.

6. Enter Token endpoint, also known as Authentication URL.

7. Click Apply.