yoyos26 opened a new issue #4317: [SLICE][RIGHT ISSUE] Problems with restricted 
rights role
URL: https://github.com/apache/incubator-superset/issues/4317
 
 
   Make sure these boxes are checked before submitting your issue - thank you!
   
   - [x] I have checked the superset logs for python stacktraces and included 
it here as text if any
   - [x] I have reproduced the issue with at least the latest released version 
of superset
   - [x] I have checked the issue tracker for the same issue and I haven't 
found one similar
   
   ![superset 
logs](https://user-images.githubusercontent.com/22061732/35615856-506f94aa-066b-11e8-9fd8-6451f149b85f.png)
   
   ### Superset version
   
   Superset version 0.22.1
   Python: version 2.7.5
   Thrift_sasl: version 0.9.3
   SQLAlchemy: version 1.2.0
   
   ### Expected results
   An user with restricted access should be able to see some slices , according 
to the rights I defined for him.
   
   ### Actual results
   Sometimes he can reads slices, sometimes not. It is random. Currently, 
today, he can't see any slices (of course he has the rights to see him)
   
   ### Steps to reproduce
   Let me show you the righs i defined for him : 
   ![restricted 
rights](https://user-images.githubusercontent.com/22061732/35616453-2c2f5ba0-066d-11e8-80fe-ea5ef958d0f7.png)
   
   
   
   Hello Everyone,
   
   I created a role who has some restricted and specific access. The goal is 
that the user who will be assigned this role, can access to some slices, 
already existants. I give to this role access to the datasource who are the 
source of data of the slice, and some others rights.
   
   The bug is, sometimes my user can see(open) the slices, sometimes only one, 
sometimes he can't see any slices.
   The only track i saw (only on one of some slices), is this following error 
message when i open the slice : Error while fetching annotation layers: 
{"message":"Access is Denied","severity":"danger"}
   
   
   Can someone help me ? :)
   

----------------------------------------------------------------
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:
[email protected]


With regards,
Apache Git Services

Reply via email to