SOLVED: Qlik Sense 2026-May-IR (client managed) breaks form based login

[mountaindude]

The other day I upgraded a client-managed Sense cluster from 2025-Nov-patch<something> to 2026-May-IR.

Upgrade finished as expected, did a reboot of all the nodes and tried to log in.
Got this:

Standard login page results in this after upgrade to 2026-May-IR

Nothing obvious in the logs (did a quick check, admittedly I may have/probably missed things..).
Rebooted all servers again - same thing. Let the system sit for a few hours, same thing.

But hey - 2026-May-patch2 is out - let's apply that. 

Again, the installers finished as expected, and surprise - after starting the various Sense services everything works again. Nice.

Something in patch1 or patch2 seems to have fixed the issue, the slightly disturbing thing is that the release notes do not really mention any fixed bugs I connect to the experienced issue.

But the issue is fixed, if anyone else comes across this issue it's worth trying an upgrade to latest patch before calling support.

Looking beyond that little upgrade speed bump, 2026-May adds quite a few nice additions, both for admins in the QMC (task history - looking at you - yay!!) and end users in the form of new and improved chart objects and other UI facing features.
Change log here.

[Eduardo_Monteiro]

Hi @mountaindude 

Please check Re: Qlik Sense May 2026 IR contains Virtual Proxy ... - Qlik Community - 2549686

I'm afraid the 2 posts might be related.

Regards,

[mountaindude · Accepted solution]

Hi @Eduardo_Monteiro 

It could be related, but I am not sure.
The issue described in the link you provided also relates to logging into Sense 2026-May, but the symptoms are different. For example, there is no anonymous login in the system I upgraded, and the issue I experiences disappeared when upgrading from 2026-May-IR > 2026-May-patch2 (without any mentioning of a fixed bug in the release notes).

I did note one thing though: 
The issue I experienced only appeared in form based login/auth.
More specifically, the virtual proxy where the login failed has "Windows" in the "Windows authentication pattern" property. But using that in a non-Windows environment makes it fall back to form based auth (i.e. a regular web page with userid/pwd entry boxes, instead of the login popup window that's shown on MS Windows computers.

So, when logging in from a macOS laptop using Chrome/Safari/Firefox/Edge that usually results in a login form being shown - and this is what failed.

When accessing the same login URL (i.e. same virtual proxy) from a Windows computer the login popup showed up - and worked for logging in. 
This was for 2026-May-IR. Once upgraded to 2026-May-patch2 the form-based login worked too.

Could be the same or related issue - or something else entirely - hard to tell.

@Sonja_Bauernfeind Good for you guys to be aware of too. But as mentioned, from what I can tell the issue has been sorted.