5 ms·
Vaultwarden commit introduces SSO using OpenID Connect
- cromka 1y agoI selfhost vaultwarden for my use only. Can someone please explain it like I am 5 what's the use case of this new feature? Is it to log in to vaultwarden using an OpenID?
- the_gastropod 1y agoYep, exactly. I selfhost Vaultwarden and a bunch of other apps that my family also use. So I run Authentik, which lets them only have to worry about remembering one login, and they then have a little dashboard of all our apps, and can click to login to whatever they want. It's a pretty decent little system, and I'm happy I can now add Vaultwarden to it. The bigger your users x applications number, the bigger the benefit. It make user management easy (e.g., you only have to manage users in one place instead of N)
- simcop2387 1y agoSame usecase for myself too. One of the biggest advantages for me is that it lets me setup a single and easily tested place for the users to reset passwords from too for when they inevitably forget or lose the post-it note. That, along with me using all the apps and not wanting to have to change 30 passwords for everything when something happens too. I went a bit more complicated myself with Keycloak instead of Authentik, simply because I knew keycloak a little better but setting up SSO for all the stuff I run has definitely been worth it.
- cycomanic 1y agoYep same for me. I actually had been holding off on Vaultwarden precisely because it didn't have sso support. A single sign on is definitely better than the having the family try to remember a different password for every app.
- input_sh 1y agoI administer it at work and now I won't have to invite a user manually, wait for them to accept the invite link via email, manually approve their account, and then assign it to groups (collections). In other words one less thing to worry about during onboarding / offboarding.
- jedahan 1y agoRun a community space that uses its own SSO, and needs to share passwords for socials and the like.
- ta1243 1y agoMy team self hosts multiple internal services, including vaultwarden. For most of these we use our standard corporate OIDC provider to provide autentication and accounting, either onto a proxy or direct on the service, that passes the user through, the hosted service is either fine (just logs the user in its local access logs for the accounting part) because it's allowed for all our corporate users, or the service uses its own authorisation logic to allow or reject the users. Some devices are just generic user/password on the device itself -- the authorisation there is that the group responsible for that device has to keep the credential secure. Any authenticated Corp user can access the login page, and that gets logged, but the authorisation is a simple user/password. If the credential isn't secure (because people are terrible with security) then at least the attacker is logged, and has had to authorise access. Some authentication is better. Our guacamole hosts for example are authenticated on proxy with OIDC, then passed through to the guacamole server which does its own authorisation based on its internal database (which itself is managed via a github approach - to add joe.bloggs@corp.com to the "Washington Servers" group you add his identity to the right part of the "groups.conf" file and when the PR is merged it applies across the estate within a minute or two). Then they can access all connections in "Washington", but "davey.jones@corp.com" isn't in that group, so can't. Likewise our IPAM will create a user in the "readonly" group automatically (our policy is ip records are available to everyone in the company), but they then need moving into an elevated rights using IPAM tooling to allocate IP addresses. Vaultwarden though we maintain separate user and password, we still have the OIDC front end, but it's completely ignored for another layer of authorisation. I'm about to go on leave so I won't be thinking too much about if this will help, but its good to have the option.
- razighter777 1y agoFantastic! I really love vaultwarden and was looking forward to this. I have no reason to run SSO in my 3 user homelab but it makes me happygood work.
- andix 1y agoA password manager is the one thing I'm very skeptical to use SSO for.
- vasco 1y agoSo you're going to play IT and duplicate all the groups and all the roles manually that already are maintained and automated for on/off-boarding? And not have them be auto-offboarded when they are let go? That introduces compliance risks and imo more problems than having SSO on your password manager. Yes, keep some master password for a rainy day if you have to, but otherwise, the more "dangerous" the thing the more it should be hooked up to SSO.
- wazzaps 1y agoIt's most useful for companies, where the goal is as much SSO as possible.
- kriops 1y agoSeparate accounts for work and private. SSO for the work account is perfectly fine for me as a dev and a big advantage for the company. But yes, don't conflate the two use cases.
- lucasyvas 1y agoDifference between work and personal. For personal, you’re right because there is nothing to bootstrap off of. But in corporate it’s provisioned to a user account that exists first. My personal bootstrap is two Yubikeys (for redundancy) that contains the password and 2FA for my Proton Pass. This plays the role of what IT would in a company with a user directory.
- jchw 1y agoFrom this PR: > A master password is still required and not controlled by the SSO From the Bitwarden documentation[1]: > Locking your vault will maintain vault data on the device, so unlocking your vault can be done offline. You will be required to enter your master password or PIN, or use biometrics, but won't need to use any active two-step login methods. That really ought to quell the majority of the concerns IMO. Though for personal usage I use KeepassXC, because not having any remote authentication at all is even simpler than SSO. [1]: https://bitwarden.com/help/vault-timeout/#vault-timeout-action https://bitwarden.com/help/vault-timeout/#vault-timeout-acti...
- Valodim 1y agoSo what is the point of this, if the user still needs a master password?
- maxvisser 1y agoMaybe if you deactiveer a users entra id that he cant access its vaultwarden vault anymore.
- cephi 1y agoAccess control -- can make it easy to add/sync users in Authentik using one username
- esseph 1y agoCan you expand the question a bit?
- deleted 1y ago[deleted]
- franga2000 1y agoCreating, deleting, blocking accounts is the main one - you only do it once for a user and they get access to all your services. It also lets you do MFA and security checks on login (like on a new device) which can prevent break-ins even if your users use easily crackable passwords.
- ethan_smith 1y agoSSO handles authentication (proving who you are) while the master password is still needed for decryption (as the encryption key is derived from it).
- jedahan 1y agoBeen using this since it was merged. No issues so far, appreciate the work.
- ronnier 1y agoI love this product have used it for a long time now but more recently started getting worried about security. I hope the maintainers are doing their due diligence around securing their docker hub account (many of us run VW in docker) and are careful about libraries the project depends on. Some questionable coding practices were made that I'm not sure I agree with (calling a 3rd party sites in some scenarios). As more of us switch to self hosting VW it will become a juicer target for bad actors. Really hoping we don't wake up one day to find out that our database was uploaded by a BA
- surge 1y agoI've threat modeled this myself, and as I understand it the Bitwarden client side decrypts/encrypts everything locally. So even if backend was entirely compromised, it's never getting anything without the master password, and that's never sent across by the client. Then again, there's also the web interface.
- ronnier 1y agoYeah if an attacker was able to insert javascript then it's possible.
- blr_lpm 1y agoFor this particular threat vector, where the client is compromised, the backend doesn’t matter.
- franga2000 1y agoA compromised server can inject exfil code into the web page it serves. If you only ever use the apps then you should be fine though.
- 9cb14c1ec0 1y agoWhich is only possible if logging into the web client and not when using the bitwarden desktop app or browser extensions.
- elashri 1y agoFor single user or family supported instances this will not make huge difference because this will still require entering master password (which is good). It would be good for cases when it would make it easier in team or company settings when the manual work to add and setup accounts with access to password collections is annoying.
- franga2000 1y agoDepending on how many services you host, this is a huge deal for family and/or friends setups. I run around a dozen things that various family members and friends use, so being able to have one accout that they can log into anything with (including password change and reset) without me having to manually manage accounts makes the whole endeavour much more viable.
- DoctorOW 1y agoMost of the comments seem to confirm (all but one at time of writing) that this feature is more intended for corporate/business environments. Does anyone know if Vaultwarden has commercial users? By no means am I arguing against the inclusion of this feature, I'm just curious. Everywhere I've worked that was big enough to use SSO was also wary of selfhosting FOSS tools. I should clarify I don't consider myself working in tech, fwiw.
- prmoustache 1y agoMy company just started hosting an instance for its employees 2 months ago.
- Disposal8433 1y agoI'm a user, not an expert on all this but: SSO is indeed meant for a corporate environment, not for personal use. And from what I saw, companies would rather pay for a simple SSO provider than use any self-hosted solution. That means you either use Google or Microsoft, nothing else. LastPass is out of question due to the security issues in the past. I always advocate for Bitwarden but I'm not sure they can handle any kind of SSO yet. And Vaultwarden, being a fork of a not-so-famous-yet password vault (at least in the managers's world), is not a contender anywhere.
- stronglikedan 1y ago> That means you either use Google or Microsoft, nothing else. My fairly large (>20k) company uses Okta. That's just to say, be wary of issuing ultimatums.
- sandeepkd 1y agoInteresting to see a PR being merged after good 2 years. Thought about the idea of reviewing the changes for self learning, however the number of files involved made me to give up on that idea soon enough. The number of comments (610) gave an impression that the PR must have been reviewed thoroughly, however a close look tells that the comments are mostly about the topic itself, not about the code changes. Unless the code review is managed internally, the PR gives an impression of mostly happy paths.
- tracker1 1y agoDefinitely cool functionality to see. I hope this doesn't pull too much from what might otherwise be Enterprise Bitwarden customers. Definitely supportive of the upstream project, while Vaultwarden seems to take less server resources to run, and simpler from what I understand. Freeing up the SSO tax.
- arjie 1y agoMostly unrelated. Does anyone know of an alternative open source extension to the Bitwarden extension? I don't mind paying for the Bitwarden service to sync etc. but the new React-based extension is incredibly slow on my M1 Max.
- xxmarkuski 1y agoHow secure is Vaultwarden?
- import 1y agoYou can read the code and see?
- pcthrowaway 1y agoI like the spirit of this comment (pointing out that it's OSS). I don't even disagree with discouraging people from asking questions that have readily searchable answers they'd be well served to direct themselves to. But I think it can be assumed that someone asking such a questions is highly unlikely to be a world-class security researcher equipped to answer it for themselves by auditing the source code, so your response comes across as snarky for the sake of snark.
- scottydelta 1y agoIt's as secure as others promise it to be but actual security is in your own hands. I self-host vaultwarden but I keep it behind a VPN. The logic is simple, Bitwarden is not there to detect intrusion attempts and safeguard your server so you gotta do it yourself, that's why its free.
- denismi 1y agoConvenient timing! I've moved my credentials over from pass to Vaultwarden about a month ago (after discovering the pass Android app was abandoned and pulled off app stores), and spent the last two weeks since discovering Pocket ID migrating a few self-hosted services to OIDC.