this post was submitted on 03 Jul 2023
16 points (100.0% liked)

Selfhosted

40692 readers
796 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud
Loki
CannaVet
devve
HybridSarcasm
[email protected]
16
VaultWarden - Am I doing it wrong? (self.selfhosted)
submitted 1 year ago* (last edited 1 year ago) by eekrano to c/selfhosted
4 comments fedilink hide all child comments
 

Hi All, Recently set up VW and imported my Keepass DB. All the folders went to "Collections" (200+ top level folders, multiple levels beneath that for some folders, about 1500 entries total) and handing out permissions to users seemed like a horrible manual experience.

Looking into this, it seems like Bitwarden has had open tickets for 5+ years for:

  • Inherited ACLs
  • Shared folders

5 years is long enough to make me think they're never coming or Bitwarden doesn't really care about these features enough to ever implement them. Of course, if they don't implement them, VW won't either as they mimic BW.

The best workaround I found was to move everything multiple people should have access to into its own vault and add users as managers to that vault. But you can't move items from one vault to another, only from a personal to a company vault- arg.

I see so much love for this app and I WANT to love it, but these (IMO) make it almost unusable for multiple users.

So how are you all handling what seems to be a serious usability issue? I want to like VW/BW, but it seems like it's missing basic functionality that every other password manager has - and even more worrying that BW don't seem to care about implementing it.

Please let me know how you're getting around these issues in a sane way that can be easily managed in the future- or if you're all just "dealing with it" or what. Thank you.

top 4 comments
sorted by: hot top controversial new old
[–] [email protected] 8 points 1 year ago

The best workaround I found was to move everything multiple people should have access to into its own vault and add users as managers to that vault.

It's also the cleanest approach.

[–] sudneo 6 points 1 year ago

Shared folders for me are an extremely rare use case (in fact, I generally don't even use folders as I rely always on the search), but the way I achieve it is creating collections for the people to share it with. For example my "sister" collection in which I put stuff that I want to share with her, and give her access. Also each user can have their own collection that they can manage, to give access to other people (so far, this has never been the case for me).

[–] [email protected] 3 points 1 year ago (1 children)

That's what the Organization feature is for. I have a organization for all the stuff I want to share with my girlfriend and just add the credentials that belong to both of us, e.g PayPal.

[–] eekrano 2 points 1 year ago

Thanks for the insight, that's good to know. What do you do if you need to move from one organization to another (it seems to be only allowed to move from personal vault to organization, not org -> personal or org -> org)