nusrath432 opened a new issue, #20774:
URL: https://github.com/apache/superset/issues/20774

   Hi,
   I am trying to test the ROW_LEVEL_SECURITY feature which is by default 
enabled in Superset:v2.0.0. However, it does not seem to work.
   
   #### How to reproduce the bug
   1. Create a role eg: `rw-examples-flights-only` with a single permission 
`datasource_access_on[examples].[flights](id:6)`
   
   2. Add a row level security filter as following:
   - Filter Type: Regular
   - Tables: `public.flights`
   - Roles: `rw-examples-flights-only` (from step 1)
   - Group Key: 
   - Clause: `AIRLINE = 'AS'`
   
   3. Add a new user as follows:
   - Firstname: Flights
   - Lastname: Analyst
   - Username: flightsanalyst
   - Is Active: Yes
   - Email: flightsanal...@email.com
   - Role: rw-examples-flights-only, sql_lab, Gamma
   - Password: <random>
   
   4. Now login as flightsanalyst user.
   
   5. Click on SQL Lab --> Database (Postgresql:examples) --> Schema (Public) 
--> See Table Schema (flights)
   
   7. Click Preview: `FLIGHTS`
   
   ### Expected results
   
   - Would expect a default `WHERE AIRLINE = 'AS'` is applied to any query on 
`flights` table and only data for `AIRLINE = 'AS'` be displayed for the logged 
in user `flightsanalyst` and should not be allowed to query data of other 
flights.
   
   ### Actual results
   
   - Data for all flights is displayed as if no `WHERE AIRLINE = 'AS'` is 
applied.
   
   #### Screenshots
   
   If applicable, add screenshots to help explain your problem.
   
   
   ### Environment
   
   (please complete the following information):
   
   - browser type and version: Chromium: Version 103.0.5060.53 (Official Build) 
snap (64-bit)
   - superset version: `superset version`: Superset 2.0.0
   - python version: `python --version`: Python 3.8.12
   - node.js version: `node -v`: 
   - any feature flags active: No feature touch - default settings of 
superset:tag:2.0.0
   
   ### Checklist
   
   Make sure to follow these steps before submitting your issue - thank you!
   
   - [X] I have checked the superset logs for python stacktraces and included 
it here as text if there are 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.
   


-- 
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: notifications-unsubscr...@superset.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


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

Reply via email to