Add support for Keycloak 24/re-encrypt Route #2261
Merged
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.
What this PR does / why we need it:
In Keycloak 24, when it is behind re-encrypt Route, any incoming http requests fail with http/500, with NPE exception saying http Host header is missing. Seems the fix is to add the proxy headers setting to parse
x-forwarded
http header.Which issue(s) this PR fixes:
Fixes https://github.ibm.com/IBMPrivateCloud/roadmap/issues/65100 and keycloak/keycloak#33988
Special notes for your reviewer:
Do fresh deploy of Keycloak 24 on ROSA cluster. Check Route
keycloak
created works fine and renders Keycloak Admin UI