mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-05-24 09:03:15 -05:00
Organization groups permission on collections are not visible in 1.32.3 #5723
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Misterbabou on GitHub (Nov 5, 2024).
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
Vaultwarden Build Version
v1.32.3
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
No proxy
Host/Server Operating System
Linux
Operating System Version
Ubuntu 22.04
Clients
Web Vault
Client Version
No response
Steps To Reproduce
(previously created group before 1.32.3 upgrade have the same issue rollback on 1.32.2 show the permission column again)
Expected Result
The permission column should print
Can View,Can Edit... depending on previous set permissionActual Result
The collumn is blank but permission previously set are working.
Logs
No response
Screenshots or Videos
Additional Context
No response
@Misterbabou commented on GitHub (Nov 11, 2024):
For info : still having the same issue on v1.32.4
@BlackDex commented on GitHub (Nov 11, 2024):
Which wouldn't be strange as that is not addressed
@Misterbabou commented on GitHub (Nov 12, 2024):
It wasn't a criticism; I just wanted to provide as much information as possible since I was referring to the previous version in my first message :)
@stefan0xC commented on GitHub (Nov 12, 2024):
Using

web-v2024.10.5(https://github.com/dani-garcia/bw_web_builds/pull/182)it seems to work as expected:As far as I've looked into it adding support for the can manage permission for groups in #5095 is responsible that it shows up in
v1.32.3because earlier web-vaults seems to be unable to handle if this evaluates totruefor groups:adb21d5c1a/src/db/models/group.rs (L85)edit: after looking again, I think that it's incorrect to use the users role for deciding the value of the group, so we should probably revert that to return just
falsefor now.@BlackDex commented on GitHub (Nov 12, 2024):
Well i think it is correct. Admins and owners are allowed to manage all groups and collections. This is also a feature option in Bitwarden. But to stay compatible with older versions and ease of working granting admins and owners full access is the right way for now.
Without this check and only returning false would make managing groups and collections break.
The only way to fix this now it's reverting the web-vault to en earlier version.
I'm working on comparing Bitwarden and Vaultwarden regarding this. But it takes a lot of time and checking and validations including making sure it keeps working if someone reverts back to an older version.
@stefan0xC commented on GitHub (Nov 12, 2024):
hm... I'll test that tomorrow.
@BlackDex commented on GitHub (Nov 12, 2024):
same here. The logic regarding the link between groups and collections is complex, more then it should be unfortunately.
@stefan0xC commented on GitHub (Nov 14, 2024):
Yeah.
With

web-v2024.6.2the permissions don't seem to be listed in the Admin Console in the collections overview, but I think this a bug in the web-vault (it might be that we don't return the correct listing but as long that this is just a visual issue I don't think it's that important).(update: seems to be only the
Can editpermission that is not shown)I've also just tried it with the new
web-v2024.11.0web-vault and it throws an error when I try to look at a group, so something seems to have changed again (but given it's a missing user error it might be unrelated to this change).