article How the Windows Authentication Pattern in Virtual Proxy enables form-based authentication in Official Support Articles

How the Windows Authentication Pattern in Virtual Proxy enables form-based authentication

Andrew_Delaney — Thu, 01 Apr 2021 12:59:45 GMT

The Qlik Sense Virtual Proxy has two different authentication options by default: Forms and Windows Authentication. The Windows Authentication Pattern setting determines which one is used.

The setting is accessed through the Qlik Sense Management Console > Virtual Proxies > [Virtual Proxy] > Authentication

See Figure 1:

When a client connects to Qlik Sense, the browser sends a User-Agent string to as part of the standard connection process.

The Qlik Sense Proxy service reads this string and checks for the presence of the value found in Windows Authentication Pattern. If the string is present windows authentication is used and if the browser supports NTLM the user may be automatically logged in. If the automatic login fails they will get a pop-up asking for username and password.

If the Windows Authentication Pattern value is not found then we fall back to forms authentication where instead we use a form and always require a username and password for login.

The default value for Windows Authentication Pattern is "Windows", which is present in all windows browser user-agent strings. If you change it to say Chrome or Firefox instead only those browsers will be offered Windows authentication. If you want to use Windows Authentication on all browsers try setting it to another string found in all user-agents (besides Windows), for example, "Mozilla".

Re: How the Windows Authentication Pattern in Virtual Proxy enables form-based authentication

pauljohansson — Tue, 27 Aug 2024 12:36:44 GMT

Hi,

We are using windows authentication pattern "Forms" & and authentication method "Ticket". This works good in general. However, randomly (idenpendent on server load) the authention stop working and noone cant authenticate, requiring a restart of the proxy service.

The proxy log don't give any more details rather than "user has specified wrong credentials?" which is we know the do. Any idea on how to understand what can be behind this? Is there some cache function with the Windows authentication pattern?

Re: How the Windows Authentication Pattern in Virtual Proxy enables form-based authentication

Sonja_Bauernfeind — Wed, 28 Aug 2024 12:02:43 GMT

Hello @pauljohansson

This seems to be a topic best posted in our Qlik Sense Deployment and Management forum, where your active Qlik peers and our support agents can better assist you.

All the best,
Sonja

Re: How the Windows Authentication Pattern in Virtual Proxy enables form-based authentication

ab_jaramillo — Wed, 20 Aug 2025 14:40:38 GMT

Hi
We currently have authentication with Windows but we want to change the configuration for SSO with SAML with Microsoft, we have followed the steps indicated in https://learn.microsoft.com/en-us/entra/identity/saas-apps/qliksense-enterprise-tutorial , but it does not work, in the virtual proxy configuration I still have the virtual proxy configuration for Windows active (I have no option to delete or modify it) and SAML.
I have configured the UDC as Generic LDAP to add the attributes and relate it to the SAML Virtual Proxy attribute. If I try to connect to https://Qlik-analytic/ it asks me for the user and password, but if I try with https://Qlik-analytic/saml/samlauthn/ it shows me the error 400.
any suggestions or solutions?

article How the Windows Authentication Pattern in Virtual Proxy enables form-based authentication in Official Support Articles

How the Windows Authentication Pattern in Virtual Proxy enables form-based authentication

Related Content:

Re: How the Windows Authentication Pattern in Virtual Proxy enables form-based authentication

Re: How the Windows Authentication Pattern in Virtual Proxy enables form-based authentication

Re: How the Windows Authentication Pattern in Virtual Proxy enables form-based authentication