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
[bitnami/keycloak] initial 'user' login results in looping reload of page, never logging in #25649
Comments
I switched from using ingressClassName "avi-lb" to "nginx" and everything started working. I'm looking into why "avi-lb" is experiencing an issue but "nginx" does not. |
Hi @lknite Thanks for sharing this info with the community. I'm unfamiliar with Avi IngressClass object, so keeping it open so you can share any advance with this. |
I got the same error with avi-lb |
Someone from avi collected a packet trace from my client system with keycloak working using nginx, and a packet trace via avi using avi-lb. Will report back once they've had a chance to look. (maybe? https://avinetworks.com/docs/latest/x-forwarded-for-header-insertion/) |
Yes the non-existence of x-forwarded-for is my privilaged track too |
For me the issue was that "HTTP-Only Cookies" was checked |
Unchecking 'HTTP-Only Cookies' also fixed it for me. |
@dgilsonAfelio do you happen to also know about gateway-api? I was trying to get gateway-api to work while I simultaneously worked to get the avi-lb ingress to work. I thought maybe unchecking "HTTP-Only Cookies" might also cause gateway-api to work but so far no luck. |
|
Name and Version
bitnami/keycloak:21.1.3
What architecture are you using?
amd64
What steps will reproduce the bug?
Standard helm deployment using values.yaml below.
Note:
Are you using any custom parameters or values?
What is the expected behavior?
Would expect to be able to login as 'user'.
What do you see instead?
After a clean deployment I have the opportunity to login as 'user'. I can see it is checking the password because if I log in with the wrong password it asks me to login again. It accepts the correct password but then continually reloads the page only showing the spinning console icon. I can see in the logs:
Additional information
The text was updated successfully, but these errors were encountered: