Skip to main content
Announcements
Accelerate Your Success: Fuel your data and AI journey with the right services, delivered by our experts. Learn More
cancel
Showing results for 
Search instead for 
Did you mean: 
Carlos_Rodriguez
Contributor
Contributor

Security Rules not applying unless Server reboots

Hey guys long time user, first time poster.

We are having a problem here where security rules are not working.  For example if you give someone access to a stream, this person cannot see it, even though in the QMC they do show up as having access.  If you remove access to a stream to another user, it does not work either, that particular user will keep the access, even though QMC shows that person as not having access.

Only after reboot of the server, do the changes apply, but the issue is not solved because you cannot do any change after that.  It seems like whatever change I do to grant or remove user access is not being taken by Qlik.

We did find this article https://community.qlik.com/t5/Qlik-Support-Updates-Blog/Security-Rules-and-Performance-in-Qlik-Sense... which mentions an issue with security rule evaluation cache.  We run a 3 node setup in our production environment, and lately one of the slave nodes needs to have the services restarted, because it goes offline.  We've had to do this for a couple of days.  I wonder if this has somehow "corrupted" the security rule evaluation cache, and that is why our rules are not applying?

 

Anybody has seen something like this, or have an idea how to fix this?  Any help will be greatly appreciated.

Thank You

Labels (1)
1 Solution

Accepted Solutions
Carlos_Rodriguez
Contributor
Contributor
Author

I was able to find a solution by working with Qlik. 

Our Production environment (multi-node) is running an older version of Qlik (September 2019) compared to our Dev and Test environments (November 2019).  We do our work on the development environment, push it to Test for QA, and when finished, the work gets pushed to Production.  All our Apps in production were not migrated.  https://support.qlik.com/articles/000086582

All apps in Production were manually migrated, followed by restarting the services in all nodes in Production.

This solved the issue.

View solution in original post

1 Reply
Carlos_Rodriguez
Contributor
Contributor
Author

I was able to find a solution by working with Qlik. 

Our Production environment (multi-node) is running an older version of Qlik (September 2019) compared to our Dev and Test environments (November 2019).  We do our work on the development environment, push it to Test for QA, and when finished, the work gets pushed to Production.  All our Apps in production were not migrated.  https://support.qlik.com/articles/000086582

All apps in Production were manually migrated, followed by restarting the services in all nodes in Production.

This solved the issue.