Example Multi-Cloud deployment to QSEoCS using Auth0 programmatic authentication or Local Bearer Token
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 (QSEoW) to Qlik Sense Enterprise on Cloud Services (QSEoCS).
Qlik Sense Enterprise on Windows (QSEoW), April 2020
Qlik Sense Enterprise on Cloud Services (QSEoCS), April 2020
!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 QSEoW to the QSEoCS environment and distributing apps. When using the local bearer token option, the auth0 programmatic ("Machine to Machine") application is not required. Skip to On QSEoW section below.
Notes: - Auth0 has recently changed the definition of Scope and calls it Permissions at the time of last update to this article. -Allowed Web Origins consists of the URL of the QSEoK deployment. If URL uses a DNS name, this has to be resolvable. Otherwise, use the IP address. The URL when deployed in Minikube and certain environments may also needs to have a matching port which is listed as ingress NodePort or LoadBalancer port in QSEoK. This can be checked by running the command "kubectl describe service qliksense-nginx-ingress-controller" or "kubectl get services"
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 QSEoCS section below.
II. Using a programmatic (Machine to Machine) auth0 application: