Skip to main content
Tenant Admin role is required to create OAuth clients. The client must also be set to the Trusted consent method — a machine-to-machine client has no user to show a consent prompt to, and until it is trusted Qlik rejects every token request.

Creating a machine-to-machine OAuth client

A machine-to-machine OAuth client lets StackOne authenticate with no signed-in user. Qlik creates a bot user for the client on its first token request and gives it Tenant Admin privileges, so anything this connection creates is owned by that bot user.

1

Create the OAuth client

Sign in to Qlik Cloud with a Tenant Admin account, then open the Administration activity center.

  • In the left sidebar, click OAuth.
  • Click Create.
The OAuth page in the Administration activity center with the OAuth sidebar item and the Create button highlighted
2

Enter the client details

On the Details step of Create new OAuth client configuration, describe the client and choose its type.

  • Name: StackOne Integration
  • Description: what the client is used for
  • Client type: Web
  • Machine-to-machine clients are created from the Web client type. You can’t change the client type after the client is created.
  • Click Next.
The Details step of the create dialog with the Client type list open and the Web option highlighted
3

Review the allowlist

The Allowlist step sets Redirect URLs and Allowed origins, which only apply when a browser is redirected back to your application. The client credentials flow never redirects a browser, so both can stay empty.

  • Click Next.
The Allowlist step of the create dialog with the Next button highlighted
4

Add the permissions

Enables actions: Activate Brand, Add Item To Collection, Assign User Or Group To A Space, Change Automation Owner, Change Automation Space, Count Users, Create A Space Share, Create Automation, Create Collection, Create Space, Create User, Deactivate Brand, Delete A Space Share, Delete An Assignment, Delete Automation, Delete Brand, Delete Brand File, Delete Collection, Delete Extension, Delete Item, Delete Space, Delete User, Disable Automation, Duplicate Automation, Enable Automation, Export Automation Run Log, Filter Users, Get Active Brand, Get An Item, Get Automation, Get Automation Run, Get Automation Usage Metrics, Get Brand, Get Brand File, Get Collection, Get Current User, Get Extension, Get Extension Archive, Get Extension File, Get Item, Get Items Settings, Get Space, Get Unified Credentials, Get Unified Group, Get Unified Organization, Get Unified Role, Get Unified User, Get User, Get User’s Favorites Collection, Invite Users, List Assignments For A Space, List Automation Runs, List Automations, List Brands, List Collections, List Collections Of An Item, List Extensions, List Items, List Items In A Collection, List Space Shares, List Space Types, List Spaces, List Unified Groups, List Unified Organizations, List Unified Resource Types, List Unified Resource Users, List Unified Roles, List Unified Users, List Users, Move Automation, Remove An Item, Retrieve A Space Share, Retrieve An Assignment For A Space, Retry Automation Run, Run Automation, Stop Automation Run, Update An Assignment For A Space, Update Automation, Update Brand, Update Collection, Update Item, Update Space, Update User

On the Permissions step, find each permission the integration needs and set it to Allowed. Setting user_default and admin_classic to Allowed covers every action this connector exposes, because they resolve to the full user and administrator permission sets. Set the narrower permissions instead if you prefer to grant least privilege.

  • Leave offline_access as Not set — the client credentials flow issues a fresh access token on each exchange and never returns a refresh token.
  • Click Next.
The Permissions step of the create dialog with a permission list open and the Allowed option highlighted
5

Enable machine-to-machine access

On the Authentication method step, turn the client into a machine-to-machine client.

  • Authentication method: Client secret
  • Select Allow Machine-to-Machine (M2M).
  • Leave Allow M2M user impersonation cleared — it is only needed to act on behalf of a named Qlik user.
  • Click Save.
The Authentication method step with the Client secret method, the Allow Machine-to-Machine checkbox and the Save button highlighted
6

Copy the client credentials

The Copy your Client ID and secret dialog appears once the client is created. Copy the Client ID and the Client secret into StackOne Hub.

  • The Client secret is only displayed once and cannot be retrieved later.
  • Click Done.
The Copy your Client ID and secret dialog with the copy buttons highlighted and the values masked
7

Set the consent method to Trusted

A new client starts on the Required consent method, which asks a signed-in user to approve the request. A machine-to-machine client has no user to ask, so it must be changed to Trusted before it can get a token.

  • On the client’s row, click the action menu (⋯) at the end of the row and select Change consent method.
  • Select Trusted - authentication using the OAuth client will skip the consent prompt.
  • Click Change consent method.
The Change consent method dialog with the Trusted option selected and the confirm button highlighted

Find your Tenant Name and Region

Your Tenant Name and Region both come from the address you use to reach Qlik Cloud. After signing in, read them from your browser’s address bar and enter them into StackOne Hub.

  • Format: https://{tenant-name}.{region}.qlikcloud.com
  • Example: https://my-company.us.qlikcloud.com/hub
  • In that example, Tenant Name is my-company and Region is us.
1

Connect

  • Click Connect.
  • If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider’s authorization flow.
  • Once authorization is successful, you will see a confirmation popup.
2

Use Actions

Connect an AI platform to the linked account’s actions. See AI Platforms.Other ways to call actions are listed in Protocols & SDKs.

Next Steps

Webhooks setup

Configure receiving Events for Qlik into StackOne.