Skip to main content

Session solution

The session solution allows the Qlik Sense Proxy Service (QPS) to use a session from an external system to validate who the user is.

All communication between the authentication module and the QPS uses Transport Layer Security (TLS) and must be authorized using certificates.

The figure below shows a typical flow for authenticating a user using a session from an external system.

  1. The user accesses the identity provider, which, for example, can be integrated into a portal. The identity provider gets the user identity and credentials and then verifies them. After that, the identity provider creates a new session.
  2. The identity provider registers the session token with the Qlik Sense session module.
  3. The identity provider sets the session token as a session cookie.
  4. The user accesses the QPS to get content (for example, through an iframe in the portal).
  5. The QPS validates the session to the session module.
  6. If the session is valid and has not yet timed out, the user is authenticated.
Tip noteThe name of the session cookie used by the authentication module can be configured in the Qlik Management Console (QMC).

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!