[GitHub] ahsanshah commented on issue #3608: Request for a filter box with user-level filtering capabilities.

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

ahsanshah commented on issue #3608: Request for a filter box with user-level filtering capabilities.
URL: https://github.com/apache/incubator-superset/issues/3608#issuecomment-362848069
 
 
   Has there been any progress on this request?  I have tried to find the "recommended" approach for data level security but not sure if anything has been published. For instance, we use Druid+Superset and there are some requests for multi-tenant id but unsure if this works as expected.  I would think having a user level permission on a specific data source is a requirement for most organizations.  Also, on FilterBoxes, allowing a user to select specific dimension values based on Role/Group would be preferable.
   
   In the meantime, how have others worked around this?  Is using a Slice or Datasource per user really feasible? How does the networking work? Proxy? Kubernetes INGRES?  
   
   Any thoughts on this are appreciated. While we use Superset internally, we cannot expand to a broader user base without this functionality.  If a User A is authorized to see a subset of a Druid Data source, how is this controlled exactly? 
   
   Thanks

----------------------------------------------------------------
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