Fix "Config" Tab Disappearance with FabAuthManager

[metalshanked]

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

• I agree to follow this project's Code of Conduct

[vikramkoka]

@vincbeck Can you please respond to this when you get a moment?

[vincbeck]

Hi @metalshanked . I am not sure I understand this issue. No config tab is defined on the Dag page (nor in the Dag run page). See definitions of tabs here. So the reason why you do not see the config tab is not because of authorization issue but because it simply does not exist :)

There is another open issue similar to the issue you are describing (but not the same), I am putting it here to be sure you are not confusing with it: #53882. If that's the case, there is already a fix for it: #53944.