SkinnyPigeon commented on issue #36439: URL: https://github.com/apache/superset/issues/36439#issuecomment-4109938060
Hey @rusackas, I finally figured this out. TL;DR, it's probably on our end but I can't figure out a nice way to resolve it. We might have misunderstood something when setting up our process many moons ago. Essentially, we have a `base` RLS filter of `1 = 0` applied to a number of our datasets as a security measure for externally facing reports. Normally, when a user sets up a new report for an external user, they create a new role, a new user, and a new `regular` RLS filter to be used for that report, which _overrides_ the `base` RLS filter. However, it would appear that the `base` filter is too clever and is applied to the underlying dataset table, even if they are in a virtual dataset, such as one saved from a query in SQL Lab. I might have been doing a bad job of testing; however, it seemed like the `regular` filter was not being applied on top of this. I will do a bit more testing when I have some time -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
