Skip to main content Skip to complementary content


All authentication in Qlik Sense is managed by the Qlik Sense Proxy Service (QPS). The QPS authenticates all users regardless of Qlik Sense client type. This means that the QPS also authenticates users of the Qlik Management Console (QMC).

Information noteIn Qlik Sense, authentication and authorization are two distinct, unconnected actions. In addition, the sources of information used for authentication do not have to be the same as for authorization, and the other way around.

Qlik Sense always asks an external system to verify who the user is and if the user can prove it. The interaction between Qlik Sense and the external identity provider is handled by authentication modules.

For a module to communicate with Qlik Sense, it has to be trusted. Transport Layer Security (TLS) and certificate authentication are used to authorize external components for communication with Qlik Sense.

In Qlik Sense, the authentication of a user consists of three distinct steps:

  1. Authentication module: Get the user identity and credentials.
  2. Authentication module: Request an external system to verify the user identity using the credentials.
  3. Transfer the user to Qlik Sense using the Ticket API, the Session API, headers, SAML, JWT, or OIDC.

The first two steps are always handled by the authentication module. It is up to the authentication module to verify the user in an appropriate way.

The third step can be performed in the following ways:

  • Using the Ticket API, which transfers the user and the user's properties using a one-time ticket.
  • Using the Session API, whereby an external module can transfer web sessions that identify the user and the user's properties to Qlik Sense.
  • Using headers, with which a trusted system can transfer the user using HTTP headers. This is a common solution for integrating with single sign-on (SSO) systems.
  • Qlik Sense can be configured to allow anonymous users (using, for example, SAML).

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!