A review of the third section of the Qlik Management Console: Integration.
Another blog entry, and another section of the Qlik Management Console. Today we will be going over the third section of QMC known as Integration.
Within this section a tenant admin can manage APIs. API keys are used by developers to gain programmatic access to the Qlik platform, acting as their own user. Admins can edit the settings for the keys as well as revoke the keys. Please note that only users with the ‘Developer’ role can generate or delete these keys. In order for someone with an ‘Admin’ status to generate or delete keys, they must assign themselves the ‘Developer’ role.
Content Security Policy
This section displays the origins and the directives of the Content Security Policy HTTP header. Here origins can be added for specific resource types to allow resources to be loaded. This section also allows users to not only add these origins and directives, but once loaded, they can be edited and deleted as well.
This section shows the OAuth clients that are used for authentication. OAuth is a standard security protocol that allows third party applications to access API resourced without disclosing the end-user credentials. This means that OAuth allows clients to use a code, instead of their log-in credentials for added security, protecting that information.
Qlik Cloud allows third-party domains to interact with your Qlik tenant. Here you can view the Name, ID, Number of Origins, Updates and Creation dates of these connections. You can also edit and delete these connections once they are added to the tenant.
Webhooks allows Qlik Cloud to send information about events in your tenant to other applications. In this section, the name of the Webhook, along with the Owner, Status, Level, Creator and Updater can be viewed. Users can also view the Endpoint URL, or the destination of these events in this section. This section also allows users to delete a Webhook.
That would be it for the fourth section of the Qlik Management Console: Integration. Thank you for giving this blog post a read, and if you see any information missing, feel free to drop it in a comment below. Join us next time where we’ll take a look at the fourth and final section: Configuration.