Logging out of Qlik Sense: Using Forms authentication to log in and out of the Sense Hub

Sonja_Bauernfeind — Thu, 17 Jun 2021 14:56:21 GMT

Qlik Sense does not automatically allow for a simple log out and may log the user back into the Hub without the need to reauthenticate. It will use windows pass-through authentication and not require manual login.

This is work as designed (WAD), since the default virtual proxy setting is using 'Windows' as 'Windows authentication pattern'. Browser caches the log in detail and reuses it once the session is recovered.

Here we will cover:

How to use a different user to log in to Qlik Sense than the currently logged in user, or
How to enable forms authentication in Qlik Sense.

Both without the need to reconfigure the currently used Virtual Proxy. A prerequisite is that we will create a new Virtual Proxy. For more information on how to configure or create a new Virtual Proxy see Qlik Sense: How to create a new Virtual Proxy

Scenario 1

Any of the following message(s) may be displayed in the QMC or Hub:

You have been logged out.

Your session has expired.

Click “Log in” to be directed to the login page

Please click login to start a session

You are not logged in to Qlik Sense

But when the user clicks "Login", they don't get the option to supply username and password but are logged in immediately.

Scenario 2

The user logging on to the Hub or QMC wants to use different user credentials than the one currently authenticated by the operating system/browser.

Resolution(s):

Solution 1

Close the browser and use use Incognito/InPrivate mode in order to refresh the login cache.

Solution 2

If not controlled by a domain Group Policy, the Integrated Windows Authentication (IWA) User Authentication setting under "Internet Options" in Control Panel may be changed to always prompt for username and password.

Control Panel > Internet Options > Security, click on the appropriate Zone, then on Custom Level.

Scroll all the way down for User Authentication options. For more information including information for Firefox browser see Integrated Windows Authentication (IWA) with Qlik using Internet Explorer, Chrome and Firefox

Close and re-open the browser for an authentication prompt where a different user account can be used.

Solution 3

Create a new virtual proxy with a new prefix and replace the default 'Windows authentication pattern' with 'forms'.

Follow these steps to ensure the proxy is correctly configured: Qlik Sense: How to create a new Virtual Proxy, including the linking to the main proxy and the adding of an engine node for load balancing.

1. Open QMC > Configure System > Virtual Proxies

2. Edit proxy > select Authentication from Properties

3. Change Windows authentication pattern from "Windows" to "Form"

4. Click on Apply

Accessing the hub or QMC is now possible through the new URL (new/hub or new/qmc).
Logging in will now always display the login page below:

article Logging out of Qlik Sense: Using Forms authentication to log in and out of the Sense Hub in Official Support Articles

Logging out of Qlik Sense: Using Forms authentication to log in and out of the Sense Hub

Qlik Sense does not automatically allow for a simple log out and may log the user back into the Hub without the need to reauthenticate. It will use windows pass-through authentication and not require manual login.

This is work as designed (WAD), since the default virtual proxy setting is using 'Windows' as 'Windows authentication pattern'. Browser caches the log in detail and reuses it once the session is recovered.

Here we will cover:

Scenario 1

Scenario 2

Resolution(s):

Solution 1

Solution 2

Solution 3

Related Content:

article Logging out of Qlik Sense: Using Forms authentication to log in and out of the Sense Hub in Official Support Articles

Logging out of Qlik Sense: Using Forms authentication to log in and out of the Sense Hub

Qlik Sense does not automatically allow for a simple log out and may log the user back into the Hub without the need to reauthenticate. It will use windows pass-through authentication and not require manual login.

This is work as designed (WAD), since the default virtual proxy setting is using 'Windows' as 'Windows authentication pattern'. Browser caches the log in detail and reuses it once the session is recovered. Here we will cover:

Scenario 1

Scenario 2

Resolution(s):

Solution 1

Solution 2

Solution 3

Related Content:

This is work as designed (WAD), since the default virtual proxy setting is using 'Windows' as 'Windows authentication pattern'. Browser caches the log in detail and reuses it once the session is recovered.

Here we will cover: