[GitHub] ahsanshah commented on issue #5128: [Question] The row-level security absence problem and it’s solving with the use of reverse proxy (OpenResty)

[GitBox <gi...@apache.org>]

ahsanshah commented on issue #5128:  [Question] The row-level security absence problem and it’s solving with the use of reverse proxy (OpenResty)
URL: https://github.com/apache/incubator-superset/issues/5128#issuecomment-394119818
 
 
   We have a similar use case using Druid.  We did consider the Proxy route where we would modify the Druid query with a extension.  However, we are currently testing passing into Superset as part of authentication/authorization specific user-defined variables (analogous to your "Region"). These can be defined in a custom superset-config.py. Once passed, the idea would be to eedit or extend the base Views to force a filter clause.    In our case the Druid issued query would have a FILTER applied so the user would see his/her relevant "records".  This is the general idea but something we are trying since Druid expects the application layer to define this.   I do agree this is something that would be great if it were standard. 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org