Skip to main content

Setting up identity providers

ON THIS PAGE

Setting up identity providers

An identity provider (IdP) manages identity information for users and provides authentication services. The identity provider enables single sign-on (SSO) so that you can access other websites, without having to log in repeatedly. In contrast to on-premises technologies, such as Active Directory and LDAP, identity providers also offer a consistent and governed experience when accessing cloud services, eliminating the need to create accounts for each new service.

Note: If user accounts are stored in Active Directory, the IdP can still enable integration into cloud software.

In Qlik Sense Enterprise SaaS or in a multi-cloud deployment, an IdP delivers the following:

  • Secure authentication of a user and a common identity (user ID and groups) passed between all deployments.
  • Common user identity to assign a license to (to avoid double use).
  • Common user ID and attributes, such as groups, to use when applying access control to content.

IdP requirements

Qlik Sense Enterprise SaaS integrates with an IdP using the OpenID Connect (OIDC) standard. This is a standard that allows both interactive login, where a user logs in via a browser, and automated login, using APIs via a software product.

Example: IdP in a SaaS deployment

Qlik Sense Enterprise SaaS and Qlik Sense Enterprise on Kubernetes are integrated with an Identity Provider via OIDC. User IDs, email, groups, and jobs are integrated through Qlik Sense Enterprise on Windows via SAML. An Identity Provider authenticates users against their identity (user ID, Password, groups).

Using an identity provider in a multi-cloud deployment

Qlik Sense Enterprise on Windows integrates with an IdP using the SAML standard or any other method that provides the IdP with a consistent user identity.

Note: An IdP implemented for a multi-cloud deployment must support both OIDC and SAML.

Example: IdPs in a multi-cloud deployment

Qlik Sense Enterprise SaaS and Qlik Sense Enterprise on Kubernetes are integrated with an Identity Provider via OIDC. User IDs, email, groups, and jobs are integrated through Qlik Sense Enterprise on Windows via SAML. An Identity Provider authenticates users against their identity (user ID, Password, groups).

For additional information on how to set up a multi-cloud deployment, see Multi-cloud Setup Console - Deployments.