Skip to content
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.

Sign up for GitHub

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

Jump to bottom

keycloak: do not invalidate session without refresh_token #704

Merged
merged 1 commit into from
Oct 7, 2022
Merged

keycloak: do not invalidate session without refresh_token #704

merged 1 commit into from
Oct 7, 2022

Commits on Oct 7, 2022

  1. keycloak: do not invalidate session without refresh_token 

    if there are multiple sessions for the same user (i.e. with different
scopes) we only get the refresh_token for the first established one and
we cannot invalidate it on first logout, so let's keep keycloak session
active until the one that established it first logs out
    @michalskrivanek
    michalskrivanek committed Oct 7, 2022
    Configuration menu
    Copy the full SHA
    72cfdb8 View commit details
    Browse the repository at this point in the history