-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Logout via OIDC not working/not implemented? #20
Comments
Hey, |
Hey had a look again and I don't think it's implemented :
|
Hey @spatical, sorry to ping you directly, but I believe you have access to a Bitwarden instance with SSO configured. |
So if it did support SLO, the expectation would be that when I log out of vaultwarden it would also log me out of my SSO provider? When I log out on vault.bitwarden.com and my SSO is attached to Google, my browser is still logged in to Google even though bitwarden is now logged out. My opinion is that the logout as is now in vaultwarden is what I would expect. |
Yes my understanding is that it should invalidate you session. But without additional configuration it might not log you out of Google. |
I would also love to see the logout flow to be implemented, e.g. for other services i can configure a logoutUrl, for authentik it is something like https://login.company.org/application/o/vaultwarden/end-session/ when redirected there users get asked to only invalidate the service session or the whole session from idp |
Hello, it will be nice to have the logout feature enabled for Keycloak, here the configuration from bitwarden: https://bitwarden.com/help/configure-sso-oidc/ |
Not sure to understand clearly the code you show me. |
When I logout from my vaultwarden web ui, I prefer logout also on my OIDC (Authelia). By example Nextcloud implements this in its application https://github.com/pulsejet/nextcloud-oidc-login with
oidc_login_logout_url
variable.Otherwise from my point of view it is a security vulnerability. Many open source tools do not implement this and clearly it is complicated to explain to non-advanced users.
The same issue on :
Really thank you for the time you spend on this issue.
Hoping that my issue doesn't delay the arrival in a release any further ;)
The text was updated successfully, but these errors were encountered: