Repository navigation
Replies: 3 comments 2 replies
|
I have a same issue. |
1 reply
|
see quarkusio/quarkus#26937 - seems to be a bug in quarkus under some circumstances |
0 replies
|
Meant to post this comment to Keycloak: quarkusio/quarkus#26937 (comment) This Exception happens if your SPNEGO credential cache is empty/expired. When will this fix be available in a released Keycloak version? I'd like to test to make sure this is the same bug/cause as I'm seeing. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I have Keycloak 17.0.0 (Quarkus) running in Kubernetes. When I start the Keycloak server with HTTP (http-enabled:true; hostname-strict-https:false), I can successfully log in to the administration console from both Windows 10 and Fedora 35 systems (tried from two computers with Windows and three with Linux). I tried both Chrome and Firefox, and the behaviour is the same.
But when I start the Keycloak server with HTTPS (certificate generated using keytool, no root certificate), then I can log in from the Fedora systems, but can't from the Windows systems.
I'm not sure if this matters, but from both the Windows and Fedora systems, I'm connecting to the Keycloak server through a corporate VPN.
When trying to log in from the Windows machines, the server returns status code 400 - this is the request URL:
In Keycloak logs, I see this exception (truncated where the three dots are for brevity):
I compared the two outgoing authentication requests (from Windows and from Fedora) in Chrome's Network tab, and they looked almost identical: small difference in accepted-language header - but only the lowest priority one, (expected) differences in session cookies.
I'd appreciate any ideas about what could be wrong with my setup.
Thanks
All reactions