Qlik Sense: Call Session API with Postman/PowerShell
This article explains how the session API works and the workflow. Postman is used to perform the API call to add the session in Qlik Sense. In the browser, developer tools or an extension can be used to set the cookie.
1. User authenticate to an external session module (This module must be built by the customer) 2. The module adds the session to the Proxy using the session API 3. The module sets the cookie for the end user 4. The end user is recognized as authenticated and can access the hub and apps.
Virtual Proxy settings:
It does not matter which authentication method is set on the virtual proxy as we are creating directly a session when using this method. However, the following information: Session Cookie header name, Authentication module redirect URI and Session Cookie domain are important to remember when you use the Session API.
In order to add a session to the virtual proxy, you need to provide the following information: UserDirectory UserId Attributes (optional, these are for example groups to which the user belongs to) Cookie value (In Qlik Sense by default, a 36 characters string such as aa051074-13a1-4f2a-842b-a64aa4d21001 is used, however this can be any value, but it must be long enough and randomized to ensure there is not 2 session cookies with the same value that are added to the virtual proxy)