-
Notifications
You must be signed in to change notification settings - Fork 6.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keycloak 24 exception http/500 on OpenShift with re-encrypt Route on ROSA #33988
Comments
@vmuzikar not sure it's within your area, can you please help here? |
The same issue happens even is reencrypt Route is put in front of the Keycloak Service created by Keycloak operator, i.e. |
Found a way of having Keycloak 24 on ROSA working with re-encrypt Route on ROSA, but still not sure why it's failing on ROSA only: apiVersion: k8s.keycloak.org/v2alpha1
kind: Keycloak
metadata:
name: cs-keycloak
spec:
...
proxy:
headers: xforwarded <--- HERE
... |
Thanks for reporting this issue, but as this is reported against an older and unsupported release we are not able to evaluate the issue. Please verify with the nightly build or the latest release. If the issue can be reproduced in the nightly build or latest release add a comment with additional information, otherwise this issue will be automatically closed within 14 days. |
I deployed into the same env upstream Keycloak v26.0.0 and I do not observe the same behavior - i.e. reencrypt Route works just fine, without myself need to specifing Can anyone explain what happened that v22 and v26 works fine, but v24 is not? |
The way proxy headers are configured changed after KC22 but apparently there was a bug that made your scenario not work that is now fixed in KC26. |
Closing this issue since it is fixed in the latest stable. |
Before reporting an issue
Area
core
Describe the bug
With Keycloak 24, deployed on ROSA (OpenShift on AWS), via RHBK operator
24.0.8-opr.1
, when Keycloak is exposed via manually created re-encrypt Route, every incoming http request fails with http/500 with stack trace:Keycloak CR
Keycloak Service
re-encrypt Route
It's similar to #28677, but actually in access logs, when enabled verbose access logs, we see that
Host
header is set:Enabled verbose access logs by setting up below env variables in Keycloak stateflset:
Version
Keycloak 24
Regression
Expected behavior
Keycloak responds successfully when using reencrypt Route
Actual behavior
Keyclak http requests are failing, despite http Host header being set correctly
How to Reproduce?
In summary included Keycloak CR, Service and Route specificiation
Anything else?
No response
The text was updated successfully, but these errors were encountered: