You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure how you got the Can Manage rights for users, since that is currently not something Vaultwarden supports, and thus have this function. It only works for Owners, Admins and Managers which have access_all rights currently, which means, for users this doesn't work.
This is the same as reported in #5361.
Which in the end means, we need to add support for this specific cbac (Collection based access control) or whatever we want to call it.
I understand that Collection based access control is not implemented yet.
However the UI behavior described above might be an issue in the future as it change Permission (at least on UI side):
For Members permission Can manage become Can edit after a save. I didn't manage to set Can manage
For Groups permission Can edit become Can manage after a save. I didn't manage to set Can edit
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Environment settings which are overridden: DOMAIN, TRASH_AUTO_DELETE_DAYS, ORG_CREATION_USERS, EMERGENCY_ACCESS_ALLOWED, ADMIN_TOKEN, INVITATION_ORG_NAME, DISABLE_2FA_REMEMBER
Config:
Vaultwarden Build Version
v1.32.7-bc913d11
Deployment method
Build from source
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
Issue 1:
Groups
and create a new group and link the new collection withCan edit
permission and pressSave
Collections
the permission show isCan manage
instead ofCan edit
Issue 2:
collections
tab link the new collection withCan manage
Permission and pressSave
Collections
the permission show isCan edit
instead ofCan manage
Expected Result
Keep the permission previously set in the web-vault
Actual Result
Can manage
becomeCan edit
Can edit
becomeCan manage
Logs
No response
Screenshots or Videos
No response
Additional Context
Thanks for the work added in #5219
The feature might not be added yet but for now, users with
Can manage
permissions (on collection) can't manage collection in the Password Manager.On Vaulwarden Side:
(note Issue 1 and 2 prevent me to have a
Can Manage
in User permission and aCan edit
in group permission)User vault:
user can't edit the Collection even if they have
Can manage
permissionOn Bitwarden side:
User vault:
User can edit the collection with
Can manage
permissionThe text was updated successfully, but these errors were encountered: