Live data from Hacker News

Vaultwarden commit introduces SSO using OpenID Connect

github.com

41–50 of 100 posts

Re: Vaultwarden commit introduces SSO using OpenID Connect

#41

Earlier quoted context omitted.

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

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?

Last time i checked you needed a MS SQL db...

Re: Vaultwarden commit introduces SSO using OpenID Connect

#42

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 workin…

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

#43

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 workin…

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…

Paid Bitwarden does SSO (SAML 2.0 or OIDC)

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

Re: Vaultwarden commit introduces SSO using OpenID Connect

#44

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 workin…

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

#45
Definitely 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.

Re: Vaultwarden commit introduces SSO using OpenID Connect

#46

Earlier quoted context omitted.

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?

Last time i checked you needed a MS SQL db...

It is all included in their Docker compose file.

Re: Vaultwarden commit introduces SSO using OpenID Connect

#47

Earlier quoted context omitted.

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?

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.

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

#48

Earlier quoted context omitted.

Last time i checked you needed a MS SQL db...

It is all included in their Docker compose file.

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

#49

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 workin…

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…

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

#50
post #28
post #23

Earlier quoted context omitted.

Yeah if an attacker was able to insert javascript then it's possible.

For this particular threat vector, where the client is compromised, the backend doesn’t matter.

A 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.
Post reply on HN