Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

From your cloud hub after login

open management console

From the side menu

choose oAuth

On Auth page press create new

The Redirect URL must be accessible from WIP cloud (Internet) in order to be able to redirect

Please keep the client id and secret key

Then go to Wip => servers => create Qlik Saas

Add

Name: ex. 01-10-QlikSaas

Url: Your Qlik Saas url (The main link used to login) EX: https://ebiexperts.eu.qlikcloud.com/

Authorization endpoint: Url + /oauth/authorize EX: https://ebiexperts.eu.qlikcloud.com/oauth/authorize

Authentication endpoint: Url + /oauth/token EX: https://ebiexperts.eu.qlikcloud.com/oauth/token

Client Id: Client Id we got in creation when configuring the Oauth in the qlik cloud server

Secret Key: Secret Key we got in creation when configuring the Oauth in the qlik cloud server

Proxy User(Super Administrator): The Email of the admin user

Proxy User Key: The Key obtained when the proxy user admin was created

Nb: Please follow the Url below for generating the proxy user key or the API key

https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Admin/mc-generate-api-keys.htm

Overview

In this tutorial, you are going to learn how to generate an API key for your account in a Qlik Sense SaaS tenant.

  • Configure API key settings for your tenant in the management console.

  • Add the developer role to a user in the management console.

  • Generate an API key

  • Test the API key in Postman

Note Only a user with the Tenant Admin role may access the management console settings and add roles to users. If you aren't the Tenant Admin of your Qlik Sense SaaS tenant, contact your Tenant Admin and direct them to this tutorial.

Configure API key settings

Note You must have the Tenant Admin role in the Qlik Sense SaaS management console to perform this section of the tutorial.

Inside the management console, click the Settings menu item on the left side of the screen.

Scroll down to the API keys section in the main part of the screen. Flip the switch to turn on API keys for the tenant, set the allowed maximum token age, and set the maximum number of active API keys a user may have in the tenant.

image-20240606-121605.png

Another requirement for generating API keys is for a user to have the developer role. In the management console menu, click Users to open the Users section and select 'Edit roles' from the elipsis menu for the user you want to add the developer role to.

image-20240606-121713.png

Check the box next to Developer to give the user developer privileges in your tenant. Save the change.

image-20240606-121758.png

Now that API keys are turned on in the tenant and the user has the developer role, have the user log in to your tenant and click the avatar in the upper-right corner of the screen. Click the API keys menu item. This action displays the API keys list for the user. Click the Generate new key button to create a new API key.

image-20240606-122102.png

Give the new API key a name and set the expiration time from the drop-down list. Click the Generate button to generate the API key.

image-20240606-122210.png

The generated API key appears. Copy it using any of the copy buttons and paste it somewhere safe.

Note The API key is only displayed once, when you create it. If you don't copy it, there is no way to see this specific key again. You have to generate a new key if you don't copy it.

image-20240606-122308.png

Take the copy of the key and use it in Create server by setting an Authorization header to use a Bearer token. Paste the key in the textbox that appears once Bearer is selected. Add a URL for a REST endpoint on the tenant. In this example, the URL is pointing to https://<tenant hostname>/api/v1/users/me. Click the Send button to make the request to the API endpoint. If you entered the information into Postman correctly, the response below appears.

  • No labels