apache/airflow

Never expose sensitive config values in UI

Chiusa

#59.860 aperta il 27 dic 2025

 (5 commenti) (0 reazioni) (0 assegnatari)Python (16.781 fork)batch import
area:APIarea:UIgood first issue

Metriche repository

Star
 (44.809 stelle)
Metriche merge PR
 (Merge medio 7g 18h) (834 PR mergiate in 30 g)

Descrizione

Body

Currently the expose config allows deployment manager to expose also sensitive data - when set to True https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#expose-config. The non-sensitive-only value causes sensitive field masking.

With the discussion mentioned in #59838 we agreed that we should never expose sensitive data over any public API where UI user can authenticate (only via task-sdk API where tasks get dedicated JWT token)

This means that:

  • Only True/False should be expected for expose-config and True means that sensitive fields are masked
  • We should add fallback - when "non-sensitive-data" is set for the parameter it should be treated as True and deprecation warning should be raised
  • newsfragment should be added explaining the behaviour change

Committer

  • I acknowledge that I am a maintainer/committer of the Apache Airflow project.

Guida contributor