You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2019/08/19 14:50:16 UTC

[GitHub] [incubator-superset] sushantmishra1996 opened a new issue #8066: Unable to view tables and charts if specific data source permission given

sushantmishra1996 opened a new issue #8066: Unable to view tables and charts if specific data source permission given
URL: https://github.com/apache/incubator-superset/issues/8066
 
 
   When maintaining permissions, by giving specific datasource access to users including gamma and alpha, the list of charts and dashboards become invisible, however, the view and tabs to access the page are present. 
   I found out that this was happening because of permission: all_datasource_access. When removing this permission, the users fail to see any list of charts and tables from their owned datasources. If given this permission they're able to access all datasources which is undesirable.
   However, they're able to see dashboards.
   
   ### Expected results
   The gamma and alpha users are able to only see slices and tables from their allotted datasource permission.
   
   ### Actual results
   
   The users do not even get the list of charts and tables specific to their allotted datasource
   
   #### Screenshots
   
   #### How to reproduce the bug
   
   1. Create specific datasource access permission ex: datasource_a
   2. Remove 'all_datasource_access' permission from alpha/gamma users
   3. Create a user with permissions : datasource_a, gamma, sqllab
   4. open the view of charts/tables/dashboards
   
   ### Environment
   
   - superset version: superset==0.29.0rc7
   - python version: Python 3.7.4
   - node.js version: `node -v`
   - npm version: `npm -v`
   
   ### Checklist
   
   Make sure these boxes are checked before submitting your issue - thank you!
   
   - [ Y] I have checked the superset logs for python stacktraces and included it here as text if there are any.
   - [Y] I have reproduced the issue with at least the latest released version of superset.
   - [Y] I have checked the issue tracker for the same issue and I haven't found one similar.
   
   ### Additional context
   
   If you can guide me onto an upcoming solution or something that I could work around with, It'd be great. Thanks.
   

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