Replies: 1 comment 8 replies
-
|
I've seen mentions of the "already logged in as " in the discussions before, but I assumed it was a cookie / caching issue that made the login form show up without properly logging out. However, this should not be the case since you mention logging out explicitly first. Are you logging out from the Keycloak account console ( |
Beta Was this translation helpful? Give feedback.
-
|
Yes user session is still logged in keycloak admin console, after sign out from UI application. |
Beta Was this translation helpful? Give feedback.
-
|
In that case, the behavior you are observing sounds like the correct one. If the logout button from the application should end the user session in the SSO, so you can log in as a different user, you will need to implement single logout / single sign-out (I think the spec is this one, but I'm not 100% sure https://openid.net/specs/openid-connect-rpinitiated-1_0.html; see also https://www.keycloak.org/securing-apps/specifications#_openid_connect). I'm not entirely sure why Keycloak 17 behaved differently; unless the authentication request is built in a manner that would prevent the SSO server from creating a user session (I think sending a request with |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your reply. I will check that if anything needed/ not clear will get back with you. But really thank you for your input. |
Beta Was this translation helpful? Give feedback.
-
|
See also #42602 and #38110 on similar subjects. You can also search the discussions tab for some keywords, maybe you find something useful. |
Beta Was this translation helpful? Give feedback.
-
|
@darius-m Sure. I will check that. If you get anything related to please share with me.. Really Thank you so much. :) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello Team,
After upgrading from Keycloak 17 to Keycloak 26.4.5, we have observed a change in session behavior across multiple tabs and sites. Below is the scenario:
Keycloak 17 Behavior:
If I log in as User 1 in Tab One for Site 1, and then open Site 2 in Tab Two, it automatically logs in with User 1 (SSO behavior).
If I log out from Tab Two and try to log in as User 2, it allows me to log in successfully.
Keycloak 26.4.5 Behavior:
If I log in as User 1 in Tab One for Site 1, and then open Site 2 in Tab Two, it also logs in with User 1.
However, if I log out from Tab Two and try to log in as User 2, it shows the error:
“You are already authenticated as a different user 'User 1' in this session. Please sign out first.”
We would like the behavior to remain consistent with Keycloak 17 (allow login with a different user after logout in the second tab). Could you please advise what is causing this change and suggest any configuration or solution to achieve the previous behavior?
Thank you for your guidance in advance.
Beta Was this translation helpful? Give feedback.
All reactions