Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Team,
Am trying to implement SAML through forgerock in my qlik cloud, while implementing when i enabled the SAML IDP it will allow all the users to login through the IDP portal, if its disabled then it will navigate to Qlik portal for the authentication, the problem is when its enabled the users who don't have to IDP portal but having access to Qlik not able to login, since it's redirecting to IDP portal, Is there any way to resolve this, I think only one IDP can be active in a tenant, but is there a way that Azure based IDP and Forgerock in a same time, i.e users who are all have access to IDP they can login, else they can login through Qlik .
Hi,
You're right in noting that currently Qlik Cloud supports only one active IdP per tenant. Once SAML is enabled and configured (e.g., with ForgeRock), all authentication requests are redirected through that IdP — and there's no native fallback mechanism to Qlik's own login or an alternative IdP like Azure AD.
If some users shouldn't authenticate via ForgeRock, but still need access, you might want to consider the following workaround:
Federation at the IdP level: You can configure ForgeRock (or Azure, depending on which one acts as the main entry point) to route users internally based on attributes like email domain or group membership. This way, you still have only one IdP configured in Qlik Cloud, but internally, users are directed to the correct authentication flow.
Another (more complex) option would be to split users into separate Qlik Cloud tenants, each with its own IdP, though this comes with its own set of limitations and overhead.
Hi,
You're right in noting that currently Qlik Cloud supports only one active IdP per tenant. Once SAML is enabled and configured (e.g., with ForgeRock), all authentication requests are redirected through that IdP — and there's no native fallback mechanism to Qlik's own login or an alternative IdP like Azure AD.
If some users shouldn't authenticate via ForgeRock, but still need access, you might want to consider the following workaround:
Federation at the IdP level: You can configure ForgeRock (or Azure, depending on which one acts as the main entry point) to route users internally based on attributes like email domain or group membership. This way, you still have only one IdP configured in Qlik Cloud, but internally, users are directed to the correct authentication flow.
Another (more complex) option would be to split users into separate Qlik Cloud tenants, each with its own IdP, though this comes with its own set of limitations and overhead.