Qlik Fix: How the Windows Authentication Pattern enables form-based authentication in Qlik Sense

Andre_Sostizzo — Mon, 15 Sep 2025 19:13:59 GMT

This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.

This video demonstrates how the Windows authentication pattern setting in Qlik Sense Virtual Proxy authentication configuration enables either Integrated Windows Authentication (IWA) or form-based authentication.

Here is a link to more information in the Support Knowledge Base:

How the Windows Authentication Pattern in Qlik Sense Virtual Proxy settings works

Video Transcript:

Hi and welcome to QlikFix.
This video demonstrates how the Windows authentication pattern setting in Qlik Sense Virtual Proxy authentication configuration enables either Integrated Windows Authentication (IWA) or form-based authentication.
With Integrated Windows Authentication, NTLM is used to authenticate the user automatically, or by prompting the user for the credentials depending on the current system Internet Options as shown here.
This happens because the default Windows Authentication Pattern value "Windows", is present in the http User-Agent request header submitted by all major web browsers when communicating with Qlik Sense.
If there is no match, form-based authentication is used in which a login page is presented to the client when accessing the Hub or QMC.
Here we use the browser's developer tools to visualize the User-Agent headers sent to Qlik Sense when using Google Chrome, Internet Explorer, Microsoft Edge, and Firefox.
Notice that they all include similar, as well as distinct content in this header.
The value configured in the Virtual Proxy configuration is checked against this header for a match.
In this case we see the word "Windows" is present in all User-Agent headers, so integrated authentication using NTLM is used.
Enabling form-based authentication is useful in certain scenarios, such as when the browser does not automatically authenticate neither prompts the client for credentials due to environmental restrictions.
As a form-based authentication example, we have created a new Virtual Proxy configured with the string "Edg" in the Windows Authentication Pattern field.
Now when using this Virtual Proxy, we can see that Integrated Windows Authentication is only used with the Microsoft Edge browser.
Using Internet Explorer and any other browser however, leads to the web form login page, as seen here.
Note however that in both cases, Windows authentication is performed in the back-end and a Ticket is obtained by the default Windows authentication module since the Authentication module redirect URI field is left blank.
If you’d like more information,
search for answers using the unified search tool on the Support Portal.
It searches across the support knowledge base, Qlik Community, Qlik Help site, and Qlik YouTube channels.
Take advantage of the expertise of peers, product experts, and technical support engineers by asking a question in a Qlik Product Forum on Qlik Community.
And don’t forget to subscribe to the Support Updates Blog.
Thanks for watching!

Attached is a downloadable .mp4 video file for those who cannot view YouTube videos.

#QlikSupport

article Qlik Fix: How the Windows Authentication Pattern enables form-based authentication in Qlik Sense in Qlik Fix

Qlik Fix: How the Windows Authentication Pattern enables form-based authentication in Qlik Sense