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.

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

Backchannel logout #121

Open
praserx opened this issue Nov 3, 2021 · 5 comments
Open

Backchannel logout #121

praserx opened this issue Nov 3, 2021 · 5 comments
Labels
complex complex change enhancement New feature or request low low priority
Projects

Comments

@praserx
Copy link

praserx commented Nov 3, 2021

Hi, I try to get working backchannel logout Keycloak feature. But requests from Keycloak (POST requests) are blocked with status code 405 (method not allowed).

If I read the code right, there is no Oauth route for POST method for logout and due to this router blocks the request. So this feature is missing. Am I right?

Thanks.

@p53
Copy link

p53 commented Nov 3, 2021

no there is no support for backchannel logout

@p53 p53 added complex complex change enhancement New feature or request low low priority labels Nov 3, 2021
@p53 p53 added this to To do in Gatekeeper via automation Oct 16, 2023
@hillout
Copy link

hillout commented Nov 7, 2023

@p53 hi, I see it's in your plan to achieve this, just out of curiosity are you willing to close this one?

@p53
Copy link

p53 commented Nov 7, 2023

gatekeeper doesn't maintain any user state, sessions (except for refresh tokens when redis store is enabled, but here purpose is different) it does use cookies for storing access/refresh tokens and it uses front channel logout mechanism because of that so not sure what you would like exactly achieve with gatekeeper and backchannel logout
@praserx @hillout could you provide example what would you like to achieve?

@p53
Copy link

p53 commented Nov 8, 2023

if you want to achieve one logout with several apps there is option for that https://gogatekeeper.github.io/gatekeeper/userguide/#session-logout

@hillout
Copy link

hillout commented Nov 14, 2023

@p53 hi, sorry for a long response. Maybe I thought that GK could listen to backchannel and initiate logout instantly, thus it's not checking user sessions by going to userinfo endpoint and thus there is less load to Kecyloak server. But since GK is mostly stateless app, than yeah, makes no sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complex complex change enhancement New feature or request low low priority
Projects
Development

No branches or pull requests

3 participants