saurabhb-dev opened a new issue, #49715:
URL: https://github.com/apache/airflow/issues/49715

   ### Apache Airflow version
   
   3.0.0
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   Summary:
   Users with role as viewer, user and public is not able see any data after 
they login instead they see forbidden error
   
   Env: 
   Airflow in Docker
   
   
   
![Image](https://github.com/user-attachments/assets/38bb5d83-1d70-4413-a6cf-a65ed7f0fb75)
   
   ### What you think should happen instead?
   
   The user with these roles (viewer, user and public) should be allowed to see 
data that they are authorized to as per RBAC permission of Airflow.
   
   ### How to reproduce
   
   Steps to reproduce:
   1. Login to your airflow 3 in docker as the admin.
   2. Create user and assign role as viewer
   3. Login as that new user in another browser and observed that you see a 
`Forbidden Error` page.
   4. Repeat the same with user roles of public and user role. Observe same 
error.
   
   ### Operating System
   
   Windows 11 Home Edition with running Airflow in docker on WSL2
   
   ### Versions of Apache Airflow Providers
   
   Default that come with Airflow 3.
   
   ### Deployment
   
   Docker-Compose
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   It happens always. As soon that the user is given another other role than 
those 3 like admin or ops, the user gets access to data on the UI.
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


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

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to