-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Organization groups permission on collections are not visible in 1.32.3 #5160
Comments
For info : still having the same issue on v1.32.4 |
Which wouldn't be strange as that is not addressed |
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 :) |
Using 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 vaultwarden/src/db/models/group.rs Line 85 in adb21d5
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 |
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. |
hm... I'll test that tomorrow. |
same here. The logic regarding the link between groups and collections is complex, more then it should be unfortunately. |
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
The text was updated successfully, but these errors were encountered: