QCS - Qlik Cloud Connection

Use the QCS connection type to analyze apps hosted in a Qlik Cloud (SaaS) instance.

Cloud Authorization Method - Choose between OAuth or API Key.

OAuth - In the Qlik Cloud Management Console, create an OAuth Client as described in "Creating an OAuth client". Use the options shown in the images below. Include as Origins all variations of your QSDA server URL, including port and http/https.

Use Qlik Login - If checked, each QSDA user logs into Qlik Cloud and QSDA runs analysis as that user. If unchecked, QSDA runs analysis as the administrative user named in "Name" (QSDA in this case).

Important note: If Use Qlik Login is unchecked, QSDA uses a userid matching the OAuth name ("QSDA" in the sample above) for the connection. If this userid does not have an assigned license, QSDA analysis consumes your tenant's capacity minutes. This may result in unexpected unavailability or extra charges in your tenant. It is highly recommended to either assign a license or check Use Qlik Login.

API Key - Use your Qlik Cloud Management Console to generate the API key. Paste the generated key in the ApiKey input box.

Web Integration ID - Required when Use Qlik Login or For Login is checked. Use your Qlik Cloud Management Console to create the Web Integration. Paste the generated ID in the Web Integration ID input box. When creating the Web Integration, include as Origins all variations of your QSDA server URL, including port and http/https. For example:

http://localhost:5003

http://dev-qlikserver:5003

https://localhost:5003``https://dev-qlikserver:5003

If a QSDA user attempts login using an Origin not in the list, the user receives this error message:

{"errors":[{"title":"returnto not included in web integration whitelist","code":"LOGIN-10","status":"401"}],"traceId":"55555555555"}

or

{"errors":[{"title":"Illegal returnto value","code":"LOGIN-8","status":"401"}],"traceId":"d06a0718b250a86e7fe58da4c55465f7"}

If For Login is checked, users must allow popups in their browser session.