Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
15 users and 2 developers have reported that they receive the below loading screen indefinitely as they attempt to enter the Qliksense Hub. Our administrators have advised us do the following:
All of these solutions work intermittently. Sometimes by switching internet browsers, from Chrome to Edge for example, one can fix the issue. But then it will reappear the following day where it worked the day before.
I wonder if it is an issue with our authentication -- which I know uses a VPN with SSO for users to enter. We started having this problem after we updated to the February 2023 Instance from the May 2021 Instance.
Has anyone else experienced this issue? Any advice you can offer besides those already mentioned?
Hello,
I guess you must edit capabilities.json.
{"contentHash":"2ae4a99c9f17ab76e1eeb27bc4211874","originalClassName":"FeatureToggle","flag":"HUB_HIDE_EMPTY_STREAMS","enabled":false}
See this article:
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.
As 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.
Hello,
We are facing the same issue with May 2024 version.
Did someone fix it?
Please let me know.
Many thanks in advance for your time.
Best Regards
Hi,
This solution https://community.qlik.com/t5/Official-Support-Articles/Error-431-when-trying-to-access-the-Qlik-Sen.... works well.
We too are facing this issue, and its very confusing. Some users are able to use the environment without a glitch - whereas others are facing this issue almost daily on the Nov 2023 and May 2024 versions.
Would be great to find the actual cause and solution.