Fix Keycloak provider redirect_uri to use HTTPS behind reverse proxy #61095
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #60922
The Keycloak authentication provider generates HTTP redirect URLs even when
running behind an HTTPS reverse proxy. This occurs because the login route
uses
request.url_for()to generate the callback URL, which doesn't respectproxy headers like
X-Forwarded-Protoby default.This fix configures Airflow to respect proxy headers by adding support for:
--proxy-headersflag withFORWARDED_ALLOW_IPSenvironment variableBoth approaches enable the Keycloak provider to correctly generate HTTPS
redirect URLs when deployed behind nginx ingress or other reverse proxies.
Testing: