Qlik Troubleshooting

This page lists common errors when connecting Sifflet to Qlik, and how to fix them.

Authentication

Qlik Rejected the Authentication

Symptom: Test Connection, Load assets, or a source run fails with:

Qlik rejected the authentication. Please check that the host is the URL of your Qlik Cloud tenant, that the OAuth client ID and secret are correct, and that the OAuth client is approved.

Cause: Qlik refused to issue an access token to Sifflet: the Host isn't the URL of a Qlik Cloud tenant, the client ID or client secret of the credential is wrong, or the OAuth client isn't approved in Qlik.

Fix:

  1. Check that the Host field is the URL of your Qlik Cloud tenant, as described in step 2.
  2. Check that the credential contains the client ID and client secret of the OAuth client created in step 1, and that the OAuth client is approved in the Qlik Cloud administration console.
  3. Click Test Connection again.

Permissions

No Qlik Spaces Found

Symptom: Test Connection fails with:

No Qlik spaces found

Cause: the OAuth client can't list any space, usually because it doesn't have the admin.spaces:read scope.

Fix:

  1. Check that the OAuth client has all the scopes listed in step 1.
  2. Click Test Connection again.

No Qlik Apps Found

Symptom: Test Connection fails with:

No Qlik apps found

Cause: the selected spaces don't contain any app, or the OAuth client can't list apps, usually because it doesn't have the admin.apps:read scope.

Fix:

  1. Check that at least one selected space contains an app.
  2. Check that the OAuth client has all the scopes listed in step 1.
  3. Click Test Connection again.

No Qlik Connections Found

Symptom: Test Connection fails with:

No Qlik connections found

Cause: the OAuth client can't list any data connection, because it doesn't have the user_default scope, or isn't a member of the spaces that contain data connections.

Fix:

  1. Check that the OAuth client has the user_default scope.
  2. Add the OAuth client as a member with the Can consume data permission to every space that contains data connections, as described in step 1.
  3. Click Test Connection again.

Lineage

No Access to the Qlik Lineage API

Symptom: Test Connection fails with:

No access to the Qlik lineage API

Cause: the OAuth client can't read the lineage of the apps of the selected spaces.

Fix:

  1. Check that the OAuth client has all the scopes listed in step 1, and is a member of the spaces that contain the apps' data connections.
  2. Click Test Connection again. If the error persists, contact Sifflet support.

Did this page help you?