potiuk opened a new pull request, #25318: URL: https://github.com/apache/airflow/pull/25318
The Google openid auth backend of ours had hard-coded way of seting the current user which was not compatible with Flask 2.2 With Flask-login 0.6.2 the user is stored in g module of flask, where before, it was stored in _request_ctx_stack. Unforatunately the google_openid rather than using _update_request_context_with_user set the user directly in context. In Flask-login 0.6.2 this stopped working. This change switches to use the _update_request_context_with_user method rather than directly storing user in context which works before and after the Flask-Login 0.6.2 change. <!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of an existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in a newsfragment file, named `{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in [newsfragments](https://github.com/apache/airflow/tree/main/newsfragments). -- 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]
