Example Multi-Cloud deployment to Qlik Sense Enterprise SaaS using Auth0 programmatic authentication or Local Bearer Token

Andre_Sostizzo — Tue, 10 May 2022 19:03:11 GMT

The following are example steps for setting up a test Multi-Cloud deployment using the Local Bearer Token or the Auth0 programmatic (machine-to-machine) authentication. This setup allows for app deployment from Qlik Sense Enterprise on Windows to Qlik Sense Enterprise SaaS.

Environment:

Resolution:

! The information in this article is provided as-is and to be used at own discretion. Ongoing support on the solution is not provided by Qlik Support.

Note: These steps assume an auth0 "Developer" account has already been created.

There are two Multi-Cloud Deployment options for integrating Qlik Sense Enterprise on Windows to the Qlik Sense Enterprise SaaS environment and distributing apps. When using the local bearer token option, the auth0 programmatic ("Machine to Machine") application is not required. Skip to On Qlik Sense Enterprise on Windows section below.

On Auth0 site:

Follow the steps under Creating an Auth0 API and application for programmatic access

Notes:
- Auth0 has recently changed the definition of Scope and calls it Permissions at the time of last update to this article.

On Qlik Sense Enterprise on Windows:

There are two options:

I. Using a local bearer token:

1. Perform the steps listed under Setup with a local bearer token.
2. Make sure to copy the local bearer token string which is referenced in the On Qlik Sense Enterprise SaaS section below.

II. Using a programmatic (Machine to Machine) auth0 application:

1. Perform the steps listed under Creating an Auth0 API and application for programmatic access.
2. Open the Multi-cloud Setup Console (MSC) on a web browser via https://<QS server name>/api/msc
3. Click on Deployments and then on + Set up new.
4. Configured the following fields:

Deployment name	QSEoCS_M2M	Give it a descriptive name
API Endpoint	https://<QSEoCS tenant name>	- <QSEoCS tenant name> is the QCS tenant name for when accessing the Cloud Hub
Audience	qlik.api	Use this a static required value.
Client ID	<Client ID>	Obtained from Auth0 under the Applications > Machine to Machine application > Settings > Client ID
Client secret	<Client Secret>	Obtained from Auth0 under the Applications > Machine to Machine application > Settings> Client Secret
Token Endpoint	https://<tenant domain>.auth0.com/oauth/token	Obtained from Auth0 under the Applications > Machine to Machine application > Settings > Advance Settings > Endpoints > OAuth Token URL

5. Click on Apply

On Qlik Sense Enterprise SaaS:

I. Using a local bearer token:

1. Logon with a tenant admin account to Qlik Sense Enterprise SaaS Management console (e.g: https://<QSEoCS tenant>.us.qlikcloud.com/console )

2. Under Configuration > Identity Providers click on Create new
3. For Type select Multi-cloud
4. Paste the Local bearer token previously copied from the MSC in to its respective box
5. Click Create.
6. Now the App distribution needs to be configured. See example under Example Multi-Cloud App distribution setup
7. See the following article on available logs for App Distribution and Deployment Setup. Multi-Cloud deployment logs and how to change logging level

II. Using a programmatic (Machine to Machine) auth0 application:

1. Logon with a tenant admin account to Qlik Sense Enterprise SaaS Management console (e.g: https://<QSEoCS tenant>.us.qlikcloud.com/console )

2. Under Configuration > Identity Providers click on Create new
3. For Type select Machine-to-Machine (M2M)
4. For Provider select Auth0
5. For OpenID configuration use https://<tenant domain>.auth0.com/.well-known/openid-configuration
6. Click Save
7. Now the App distribution needs to be configured. See example under Example Multi-Cloud App distribution setup
8. See the following article on available logs for App Distribution and Deployment Setup. Multi-Cloud deployment logs and how to change logging level

9. If setting up Multi-Cloud distribution, in a multi node environment. It is possible to disable the Distribution from RIM nodes but not on the central node. This can be done as follows;

In file : C:\Program Files\Qlik\Sense\ServiceDispatcher\Services.conf
Modify the file content to disable the services by adding "Disabled=true" for both services.

[appdistributionservice]
Disabled=true
Identity=Qlik.app-distribution-service
DisplayName=App Distribution Service
ExePath=dotnet\dotnet.exe
UseScript=false

[hybriddeploymentservice]
Disabled=true
Identity=Qlik.hybrid-deployment-service
DisplayName=Hybrid Deployment Service
ExePath=dotnet\dotnet.exe
UseScript=false