Hello, I am sending this email to gather feedbacks/concerns on what is going to happen regarding AIP-56 (https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-56+Extensible+user+management). The majority of the work related to AIP-56 is now completed. As a summary, all the code related to user authentication and user authorization has been packaged in a new component called "FAB auth manager" (https://github.com/apache/airflow/blob/main/airflow/auth/managers/fab/fab_auth_manager.py). Now, all user authentication and user authorization operations are done in this FAB auth manager. The purpose of having this new component is to be able to plug (and/or create) another "auth manager" if desired.
For simplification reasons, this FAB auth manager is still in core Airflow under "airflow.auth.managers.fab" (https://github.com/apache/airflow/tree/main/airflow/auth/managers/fab) but the ultimate plan is to move the module "airflow.auth.managers.fab" to a new provider. Of course, this new provider would still be installed by default in Airflow and will have no impact for the users. An issue had been created for that work and a discussion has started but I wanted to increase the audience and potentially get more feedbacks/concerns before actually doing so: https://github.com/apache/airflow/issues/32210. In this issue you will also find the motivations behind moving this code to a new provider. Cheers, Vincent
