kilian-le-calvez opened a new issue, #56470: URL: https://github.com/apache/airflow/issues/56470
### What do you see as an issue? Hello, I just struggled a long time because i was blindly testing configuration to upgrade my airflow project to 3.X using sqlalchemy 2.X. Specs are: Docker file with image FROM apache/airflow:3.1.0-python3.12 following the official 3.1 docker-compose file having sqlalchemy in my requirements: sqlalchemy==2.0.36 What i struggled with: The Fab Auth Manager (old) is still active but not working for sqlalchemy 2.X The Simple Auth Manager is easy to use but provide only authentification for the UI login. Since now there is JWT authentification, the worker could not verify the jwt when trying to launch a DAG. ### Solving the problem You have to go through all the following configuration page: https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html To find the: Environment Variables: AIRFLOW__API_AUTH__JWT_SECRET That will enable the worker jwt sign effectively. But this is not referenced in the official docker-compose file since it use fab auth manager (which is incompatible with sqlalchemy 2.X) Could you please add a doc page that the reference a working setup using simple auth manager ? Because some people might also need to use sqlalchemy 2.X and took me very much time to find the good working information. ### Anything else Only relevant for people that want to use sqlalchemy 2.X and so upgrading airflow to 3.X without using fab auth manager (old using sqlalchemy <2.0) This is one of the first issue i submit, that's just requesting a doc for a specific use case so i did not linked all my config and showing code. Thank you very much for your time ### 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]
