metalshanked opened a new issue, #53902:
URL: https://github.com/apache/airflow/issues/53902

   ### Apache Airflow version
   
   3.0.3
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   Airflow's pluggable authentication framework allows for custom authorization 
managers. However, where implementing a custom auth manager based on 
FabAuthManager causes the "Config" tab on the DAG view page to be hidden, even 
for users with full permissions. This prevents users from inspecting the 
computed configuration of a DAG run, which is a critical debugging and 
operational tool. The issue likely stems from a missing or incorrect permission 
check in the UI rendering logic.
   
   ### What you think should happen instead?
   
   _No response_
   
   ### How to reproduce
   
   Trace the UI rendering logic for the DAG view page to identify the 
permission check that controls the visibility of the "Config" tab. This is 
likely a frontend check in the React application and a corresponding backend 
permission check in the Flask views.
   
   The required permission is likely can_read on the Configurations resource.
   
   The bug is probably that this permission is not being correctly associated 
with default roles when a custom auth manager is in use.
   
   The fix may involve ensuring that the necessary permission is correctly 
registered and checked, or adjusting the UI component to rely on a more general 
DAG-level permission if appropriate.
   
   ### Operating System
   
   Ubuntu
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### 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