News for hackers. Stuff that matters.
Re:Vaultwarden commit introduces SSO using OpenID Connect by DoctorOW on Friday August 15, 2025 @11:32AM (#44913632)
Most 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.
Re:Vaultwarden commit introduces SSO using OpenID Connect by raybb on Friday August 15, 2025 @12:06PM (#44914103)
As someone who manages the vault warden instance for a nonprofit with many volunteers but no fulltime employees I see this as a wonderful thing. Yes bitwarden has a nonprofit discount but no playing wack a mole with which of the 20+ volunteers are active at any moment to avoid getting a huge bill isn't worth it vs self hosting.
Re:Vaultwarden commit introduces SSO using OpenID Connect by prometheon1 on Saturday August 16, 2025 @04:19AM (#44921335)
I'm in a similar situation, having many volunteers does not mean we have the budget to pay 5-10 euros per month for all of them for all the tools needed for work. Self-hosting and managed hosting of open-source software are the best option for us, including SSO and password management
Re:Vaultwarden commit introduces SSO using OpenID Connect by Disposal8433 on Friday August 15, 2025 @11:48AM (#44913842)
I'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.

Re:Vaultwarden commit introduces SSO using OpenID Connect by stronglikedan on Friday August 15, 2025 @12:04PM (#44914068)
> 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.

Re:Vaultwarden commit introduces SSO using OpenID Connect by tracker1 on Friday August 15, 2025 @01:00PM (#44914766)
I recall a happy/fun environment using Microsoft Entra (Azure AD) SSO, in order to sign into Okta SSO, in order to access Azure environment(s), among other apps. SSO Inception.
Re:Vaultwarden commit introduces SSO using OpenID Connect by maxwellg on Friday August 15, 2025 @04:24PM (#44916920)
SSO chaining is super common in large corporate environments. Different orgs might have their own SSO IDP, acquisitions often bring their own, etc. Once a provider is in use, it is quite difficult to tear out later while keeping everyone in their proper accounts in all the apps that tie in. Many apps are really bad at SSO migrations, or deduplicating multiple SSO identities to a single user account.
Re:Vaultwarden commit introduces SSO using OpenID Connect by threePointFive on Friday August 15, 2025 @12:58PM (#44914727)
My company just implemented the SaaS Bitwarden with Google SAML on their Enterprise Plan. Very easy to set up, not too expensive ($6/user/month). Their compliance page made it much easier to sell to my manager who had to give the final approval: https://bitwarden.com/compliance/. It is only used by my department so far and we're still doing manual invites rather than integrating with the SCIM features so I can't speak to that. My biggest annoyance is that, as an admin, unlocking the vault still prompts for the master password rather than letting me select SSO without logging all the way out.
Re:Vaultwarden commit introduces SSO using OpenID Connect by FuriouslyAdrift on Friday August 15, 2025 @01:10PM (#44914901)
Paid Bitwarden does SSO (SAML 2.0 or OIDC)

https://bitwarden.com/help/about-sso/

Re:Vaultwarden commit introduces SSO using OpenID Connect by franga2000 on Friday August 15, 2025 @01:43PM (#44915292)
The whole "SSO is meant for enterprise" thing is sales bullshit. Big enterprises can't live without SSO, so everyone started charging extra for that to milk more money out of them, but this doesn't mean it's not hugely beneficial or "meant for" smaller orgs or even individuals.

Anyone can spin up an Authentik/Authelia/Keycloak/whatever instance or even use Microsoft/Google if they already pay for it in a matter of minutes. The only reason people don't is because tons of apps make it annoyingly difficult to integrate SSO or don't offer it at all in the lower price tiers.

If app installers started with "create a root user or paste the OIDC secret here", everyone and their dog would be running SSO. But that's not as profitable.

Re:Vaultwarden commit introduces SSO using OpenID Connect by ffsm8 on Friday August 15, 2025 @02:49PM (#44916123)
Vaultwarden is not a fork though?

And also, in what world is SSO meant for enterprise?

It's Single Sign On, not having to login separately for each service is perfect for any context of any size - wherever these services only have 1 user or 100 thousand.

Re:Vaultwarden commit introduces SSO using OpenID Connect by preisschild on Friday August 15, 2025 @12:19PM (#44914250)
Vaultwarden is a lot easier to self host than Bitwarden

But like all community-made open source stuff, If you want to use it for "production" stuff you should invest in audits and contribute/fund development

Re:Vaultwarden commit introduces SSO using OpenID Connect by warkdarrior on Friday August 15, 2025 @12:36PM (#44914476)
I've been self-hosting Bitwarden (and giving them money) for a few years now, it is really easy with Docker and a reverse proxy. What kind of challenges did you encounter with Bitwarden?
Re:Vaultwarden commit introduces SSO using OpenID Connect by fkyoureadthedoc on Friday August 15, 2025 @01:04PM (#44914818)
Vaultwarden uses fewer resources and runs fine on a $5 digital ocean VPS where I had some issues with Bitwarden. I hardly have to remember that I'm running it myself.
Re:Vaultwarden commit introduces SSO using OpenID Connect by warkdarrior on Friday August 15, 2025 @01:17PM (#44914981)
Resource usage is a fair point. My home computer is 64 cores and 1TB RAM so I don't even notice Bitwarden running.
Re:Vaultwarden commit introduces SSO using OpenID Connect by preisschild on Friday August 15, 2025 @01:06PM (#44914849)
Last time i checked you needed a MS SQL db...
Re:Vaultwarden commit introduces SSO using OpenID Connect by aaronax on Friday August 15, 2025 @03:01PM (#44916236)
https://bitwarden.com/help/database-options/

"All Bitwarden self-hosted server deployments, except for unified, ship with an MSSQL Express image by default."

Re:Vaultwarden commit introduces SSO using OpenID Connect by cheema33 on Friday August 15, 2025 @02:40PM (#44916020)
> Last time i checked you needed a MS SQL db...

For real? That would mean a requirement for a software license that costs about $1,000 for the cheapest option.

Re:Vaultwarden commit introduces SSO using OpenID Connect by warkdarrior on Friday August 15, 2025 @01:15PM (#44914966)
It is all included in their Docker compose file.
Re:Vaultwarden commit introduces SSO using OpenID Connect by preisschild on Friday August 15, 2025 @01:19PM (#44915012)
I use Kubernetes

But also what about the whole lifecycle?

I can easily deploy a HA Postgres cluster that is backed up for me. I'd have to do the same thing to back up BW.

Re:Vaultwarden commit introduces SSO using OpenID Connect by warkdarrior on Friday August 15, 2025 @09:42PM (#44919306)
Don't know much about HA (it looks like Bitwarden does this through Helm https://bitwarden.com/help/self-host-with-helm/), but backup is a matter of simply copying files: https://bitwarden.com/help/backup-on-premise/
Re:Vaultwarden commit introduces SSO using OpenID Connect by seized on Friday August 15, 2025 @07:08PM (#44918303)
There is a new Unified one that can use SQLite and other options. I have been using that one for a year or more
Re:Vaultwarden commit introduces SSO using OpenID Connect by c0balt on Friday August 15, 2025 @12:38PM (#44914498)
I'm hosting it for our team at a public institute, we are strongly supportive of OSS and have interest in keeping our data on premise.

Team of <10 though so hosting is trivial with NixOS. We also have almost no money available for purchasing software so official self-hosted bitwarden was not an option unfortunately (if we had money, that would've been the way to go).

Re:Vaultwarden commit introduces SSO using OpenID Connect by homebrewer on Friday August 15, 2025 @12:46PM (#44914599)
I support an installation for a couple hundred users. It's been working fine for several years now, including browser plugins and mobile clients. If the project goes under, it's easy to export everything and import into the official Bitwarden.

(Whose server I really don't enjoy, it's very enterprise-y and heavy on resources for no real reason I could find.)

Re:Vaultwarden commit introduces SSO using OpenID Connect by kuschku on Friday August 15, 2025 @01:06PM (#44914852)
SSO is really important in the "few tools, many users" case, but just as important in the "many tools, few users" case. I'm self hosting dozens of tools, and without SSO I'd have to set up username, password, TOTP and WebAuthn for each and every one of them, my 2FA app would be 90% my own services.

With SSO though, it's much simpler. I can just run an OIDC server and log into all my self-hosted services once, and I can use all of them. Vaultwarden is an exception to the rule though, as you can't really bootstrap that in the individual case.

Another use case I'm currently exploring is for sharing netflix/prime/disney+ passwords with roommates, partners and friends. They just sign in with their Google/Apple/whatever account and get access to the shared streaming provider passwords.

Re:Vaultwarden commit introduces SSO using OpenID Connect by arjvik on Friday August 15, 2025 @02:27PM (#44915862)
What's your (OSS?) OIDC server of choice?

Authelia? Authentik? Keycloak? (These are the three I see a lot about.) Something else?

Re:Vaultwarden commit introduces SSO using OpenID Connect by thedanbob on Friday August 15, 2025 @04:15PM (#44916837)
Adding another +1 to Pocket ID. I looked at a couple of the ones you mentioned but they looked too heavy and complex for what I wanted. Pocket ID does one thing and does it well.
Re:Vaultwarden commit introduces SSO using OpenID Connect by samgnesin on Friday August 15, 2025 @03:37PM (#44916560)
Pocket ID[1] is what I use, and I cannot recommend it enough. It's an incredible project.

[1] https://pocket-id.org

Re:Vaultwarden commit introduces SSO using OpenID Connect by udev4096 on Saturday August 16, 2025 @02:00AM (#44920618)
Love pocket-id. Do you use oauth2-proxy with it? How did you set up oauth2-proxy to work with multiple apps?
Re:Vaultwarden commit introduces SSO using OpenID Connect by carlhjerpe on Saturday August 16, 2025 @08:05AM (#44922520)
I've dabbled in oauth2-proxy but I'm not running it currently. I recall my goto was launching one instance per remote i want to target.
Re:Vaultwarden commit introduces SSO using OpenID Connect by udev4096 on Saturday August 16, 2025 @08:19AM (#44922617)
Yeah that's hard to scale when you have lots of services. For now, I am running multiple instances of oauth2-proxy instances and assigning user groups in pocket-id. How do you deal with apps not having native OIDC support?
Re:Vaultwarden commit introduces SSO using OpenID Connect by gh02t on Saturday August 16, 2025 @11:01AM (#44924057)
I used to use oauth2-proxy with PocketID, but migrated to caddy-security for stuff that doesn't directly support OIDC as part of a general move to Caddy. It's nice not needing the sidecar container, though the docs for caddy-security are a bit confusing and I still find Caddy's whole approach to plugins a bit... odd. It does give you quite a lot of flexibility once you figure it out, and I think it was worthwhile after the initial learning period.
Re:Vaultwarden commit introduces SSO using OpenID Connect by gh02t on Friday August 15, 2025 @03:24PM (#44916458)
For self hosting, PocketID is about as easy to set up and maintain as it gets.
Re:Vaultwarden commit introduces SSO using OpenID Connect by mmcnl on Friday August 15, 2025 @02:47PM (#44916100)
I've used Authelia for a few years and it's great. It does exactly what I need/want. Not more, not less. It's also never failed me.
Re:Vaultwarden commit introduces SSO using OpenID Connect by eloh on Friday August 15, 2025 @02:45PM (#44916076)
Can recommend Kanidm
Re:Vaultwarden commit introduces SSO using OpenID Connect by sp0ck on Friday August 15, 2025 @03:27PM (#44916487)
Kanidm made some weird decision that ruled it out in one of big organisation I try to deploy it. Separate Radius password. For telco that’s half its use cases, and there is separate random password. Whole Network engineering department was like WTF ? You can’t have single password which is one of important reasons to have SSOA.
Re:Vaultwarden commit introduces SSO using OpenID Connect by gallexme on Friday August 15, 2025 @06:45PM (#44918150)
Mine is zitadel
Re:Vaultwarden commit introduces SSO using OpenID Connect by timc3 on Saturday August 16, 2025 @02:39AM (#44920808)
I use Authelia backed by lldap. Really like it so far
Re:Vaultwarden commit introduces SSO using OpenID Connect by Timshel on Friday August 15, 2025 @01:13PM (#44914937)
Started working (based on previous work already done) then maintaining the PR for my personal self-hosted stack.

Had then some fun adding roles/groups support (not yet merged).

Re:Vaultwarden commit introduces SSO using OpenID Connect by toomuchtodo on Friday August 15, 2025 @02:05PM (#44915573)
SSO isn’t an enterprise feature, it is an access control and governance feature regardless of user population.
Re:Vaultwarden commit introduces SSO using OpenID Connect by rat9988 on Friday August 15, 2025 @02:18PM (#44915736)
Who needs it except entreprises for the 99.99% usecase?
Re:Vaultwarden commit introduces SSO using OpenID Connect by arjvik on Friday August 15, 2025 @02:28PM (#44915877)
E.g. the homelab admin who doesn't want their family to have to create and manage accounts on 12 different self-hosted services.
Re:Vaultwarden commit introduces SSO using OpenID Connect by mcpherrinm on Friday August 15, 2025 @02:55PM (#44916179)
Everyone from the single-user homelab to the biggest companies should have SSO.
Re:Vaultwarden commit introduces SSO using OpenID Connect by cyberax on Friday August 15, 2025 @02:36PM (#44915969)
Self-hosters so you don't need to record 100 different passwords for your own services?
Re:Vaultwarden commit introduces SSO using OpenID Connect by prmoustache on Friday August 15, 2025 @07:44PM (#44918557)
My company just started hosting an instance for its employees 2 months ago.
Re:Vaultwarden commit introduces SSO using OpenID Connect by BirAdam on Friday August 15, 2025 @10:08PM (#44919494)
Vaultwarden has been in use at two companies I’ve worked for, yeah. Modest, mid-size companies, one with a delusion of grandeur. While both didn’t care for self-hosting, the executives were wary, in both cases, of SaaS password management after LastPass.
Re:Vaultwarden commit introduces SSO using OpenID Connect by kriops on Saturday August 16, 2025 @09:26AM (#44923214)
I’ve used it at a previous job. SMB, ca. 200(?) employees.
Re:Vaultwarden commit introduces SSO using OpenID Connect by chrissssdotcom on Sunday August 17, 2025 @03:49AM (#44929740)
Same here! - 350-400 employees, but the main requirement was that it could be accessed with no internet. Came from Keepass, love it. SSO just makes it better.
Re:Vaultwarden commit introduces SSO using OpenID Connect by Gormo on Saturday August 16, 2025 @04:30PM (#44926673)
> Does anyone know if Vaultwarden has commercial users?

Yes, it does.