Repository navigation
Tying Keycloak session to external IdP/OP session validity #42741
Unanswered
segevfiner
asked this question in
Q&A
Replies: 0 comments
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.
As far as I understand it, if and external IdP/OP doesn't somehow trigger logout from Keycloak, the session in Keycloak will remain valid regardless if the session in the IdP/OP has otherwise expired or logged out. Is there any way to tie the sessions together so that at least when doing something like refreshing the token it will be detected that the remote session expired for any reason (Such as the user changing his password, not active for a long time, etc) and as such reject the refresh and require sign in again? Or are sessions always independent like this?
Is this something any Idp/OP does or they all just rely on SLO if at all? (Asking since SLO seems poorly supported in many services, with them only supporting front channel, but third party cookies being partitioned/blocked by default in major browsers, or even not supported at all)
All reactions