Replies: 3 comments 1 reply
-
|
bump |
Beta Was this translation helpful? Give feedback.
-
|
bump |
Beta Was this translation helpful? Give feedback.
-
|
Have you made changes to the browser authentication flow or disabled accepting cookies in your browser? When you already authenticated and directly navigating the site you are sending headers to maintain your session, but if you refresh or enter an admin console url directly it must rely on a cookie to keep the session. |
Beta Was this translation helpful? Give feedback.
-
|
I see you closed this as resolved 5 months ago. Did the behaviour just disappear for you, or did you change something? We're also observing this behaviour in one of our clusters and are currently unsure why, @jpstone |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
For Keycloak 26.0.7, when I'm in the admin console, a page refresh redirects me to the login screen. Everything works inside the console, so the session is still alive, it's just a page refresh causes me to be redirected to the login screen.
When I Iook at the netork tab, the redirect to the openid auth endpoint has the following param:
error=login_requiredWhen I redeploy Keycloak, there is a slim chance this issue will stop happening (about 1 in ever 20 deployments or so).
To eliminate the new persistent sessions as a possible culprit, I started Keycloak with
--features-disabled=persistent-user-sessions, but the issue was still present.This issue happens regardless if I upgrade from 16 to 26.0.7 or just install 26.0.7 fresh.
Any help is appreciated.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions