somas193 commented on issue #54098: URL: https://github.com/apache/airflow/issues/54098#issuecomment-3163093747
@potiuk, you are right; the maintainers, code contributors, and users together make up the Airflow community, and it is not right on my part to single out a certain set of people. I have corrected my comment above to reflect this. I am really thankful to the Airflow maintainers, contributors, and other members of the community for providing a robust workflow manager with multiple features, constant updates to support the latest trends, and making it available as open source software. I am aware that FAB has its own documentation and set of examples for different authentication mechanisms, including OAuth, and I did refer to it while working on the integration of Authentik with Airflow. However, there is also the aspect of how Airflow has integrated FAB within it, and that is where things are still a bit unclear to me. Looking at some of the recently open/closed issues related to FAB, I got to know a few things, such as the existence of a separate UI Auth and API Auth, shift of environment variables/packages related to FAB, deprecation of `webserver_config.py` type files for specifying custom authentication details, and so on. However, it's an ongoing process to understand all the changes related to webserver/api server and authentication mechanisms in AIrflow v3. It is understandable that there will be breaking changes in major version changes, and I suppose it is the responsibility of the community as a whole to overcome the bugs and lack of documentation. I myself would be happy to provide some contribution once I have a better understanding of Airflow internals and also of authentication mechanisms. I think the Keycloak-related example provided [here](https://airflow.apache.org/docs/apache-airflow-providers-fab/stable/auth-manager/webserver-authentication.html) is very helpful. What would be even better is if we could update it to reflect how such an authentication mechanism can be implemented in Airflow v3+. Also, I would like to know more about the KeyCloak Auth-manager that might be available in Airflow 3.1. Is it supposed to be a generic auth manager like FAB that can support different authentication providers/mechanisms, or will it only support Keycloak based mechanisms? -- 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]
