Live data from Hacker News

Vaultwarden commit introduces SSO using OpenID Connect

github.com

21–30 of 100 posts

Re: Vaultwarden commit introduces SSO using OpenID Connect

#21
post #2

I 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?

I 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.

Re: Vaultwarden commit introduces SSO using OpenID Connect

#22
post #18

I 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 mor…

If you're running on kubernetes, a simple network policy and blocking the container from using DNS will stop any compromised image from performing a data exfill.

I do this for most containers.

If the container must have web access in some form, setup a squid proxy and only whitelist safe and trusted domains that can't be exfilled to.

Re: Vaultwarden commit introduces SSO using OpenID Connect

#23
post #20
post #18

I 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 mor…

I'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.

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

Re: Vaultwarden commit introduces SSO using OpenID Connect

#24
post #18

I 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 mor…

If you're running on kubernetes, a simple network policy and blocking the container from using DNS will stop any compromised image from performing a data exfill. I do this for most containers. If the container must have web access in some form, setup a squid proxy and only whitelist safe and trusted domains that can't be exfilled to.

I use Docker (in Unraid).

Re: Vaultwarden commit introduces SSO using OpenID Connect

#25
For 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.

Re: Vaultwarden commit introduces SSO using OpenID Connect

#26
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

#27
post #18

I 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 mor…

If you're running on kubernetes, a simple network policy and blocking the container from using DNS will stop any compromised image from performing a data exfill. I do this for most containers. If the container must have web access in some form, setup a squid proxy and only whitelist safe and trusted domains that can't be exfilled to.

> a simple network policy and blocking the container from using DNS

Can you please point to some resources that can help with how to do this?

Re: Vaultwarden commit introduces SSO using OpenID Connect

#28
post #23
post #20

Earlier quoted context omitted.

I'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.

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.

Re: Vaultwarden commit introduces SSO using OpenID Connect

#29

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

#30
post #2

I 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?

Run a community space that uses its own SSO, and needs to share passwords for socials and the like.
Post reply on HN