Qlik Sense May 2024 - Some user are stuck on hub loading

[OlivierS]

Hi,

A qlik server just have been upgrade to may2024 version and a strange bug seems to happen to certain users.

While some users have no issue to connect to qlik and work on it, others are totally stuck on the "loading" process to the hub.

I tried to empty the cache, check the log that show that user succesfully connect to qlik.....I have no clue on what is happening here. I have found several post on the community regarding such a bug in 2014 but i can't be sure this is about the same problem.

Any clue ?

[mpc]

Hi, 

Quite strange indeed, can you share the browser console (F12) of an user who have an issue ? 

Kind regards

[Or]

This post from a year ago was just floated this week on a similar issue:

https://community.qlik.com/t5/Deployment-Management/Qliksense-Hub-not-loading-Began-after-update-to-...

[OlivierS · Accepted solution]

We had to make a roll back for that situation so the update was not possible. It is our understanding that the cookie obtained by the Azure Auth was exceending qlik limit (related to an error found into the brower console).

Basically the three profile where part of a few azure groups while all the other had much more.

No other problem could be pointed after carreful analysis of the logs. 

Just want to point out we lost countless hours checking the community while no direct source for troubleshooting is available.....

[OlivierS]

those solution have been tested and couldn't solved the issue

[LRuCelver]

Thanks for the tip with the number of ad groups.

Restricting the groups to Security Groups only solved the issue for us.

[tens]

Hi community,

I can confirm that I was able to reproduce this bug tool. By using SAML Azure AD authentification when user get many groups, I encountered the same issue. I'll open a ticket at support. The limit seems to be around 30 groups maybe the number depends about the other attributes mapping.

Qlik Solution

When there is too much group, all api requests answer HTTP/1.1 431 Request Header Fields Too Large. 

The solution we used https://community.qlik.com/t5/Official-Support-Articles/Error-431-when-trying-to-access-the-Qlik-Sen... it works well.

Entra ID Solution

Entra ID solution we found is to limit the number of group returned in the token, but you need to have a paid Entra Id. 

[tens]

Hi community,

I can confirm that I was able to reproduce this bug tool. By using SAML Azure AD authentification when user get many groups, I encountered the same issue. I'll open a ticket at support. The limit seems to be around 30 groups maybe the number depends about the other attributes mapping.

Qlik Solution

When there is too much group, all api requests answer HTTP/1.1 431 Request Header Fields Too Large. 

The solution we used https://community.qlik.com/t5/Official-Support-Articles/Error-431-when-trying-to-access-the-Qlik-Sen... it works well.

Entra ID Solution

Entra ID solution we found is to limit the number of group returned in the token, but you need to have a paid Entra Id.