mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2025-12-10 17:23:04 +03:00
“Can edit” becomes ”Can manage” #243
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 @sbdiun on GitHub.
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, SIGNUPS_ALLOWED, ORG_CREATION_USERS, YUBICO_CLIENT_ID, YUBICO_SECRET_KEY, SMTP_HOST, SMTP_PORT, SMTP_FROM, SMTP_FROM_NAME
Config:
Vaultwarden Build Version
1.33.0
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
Apache 2.4.62-1.el9_5.2
Host/Server Operating System
Linux
Operating System Version
AlmaLinux 9.5 (Teal Serval)
Clients
Web Vault
Client Version
v2025.1.1
Steps To Reproduce
Expected Result
It is expected that the “Can edit” right is still displayed for the user/group.
Actual Result
“Can manage” is written as permission.
If you check in another session with one of the users who is in the group whether they have the “Can manage” right, you will see that the desired “Can edit” right is active (so you cannot change anything in the collection information or access)
But if you click on “Save”, the user/group really gets the right “Can manage” - which can easily be overseen if, for example, you actually want to add a new group
Logs
Screenshots or Videos
[2025-01-29 15:45:11.280][request][INFO] GET /api/organizations/d09fb8b4-29e9-4cf8-af62-f92f7fc3d4bb/groups
[2025-01-29 15:45:11.281][request][INFO] GET /api/organizations/d09fb8b4-29e9-4cf8-af62-f92f7fc3d4bb/collections/details
[2025-01-29 15:45:11.282][request][INFO] GET /api/organizations/d09fb8b4-29e9-4cf8-af62-f92f7fc3d4bb/users/mini-details
[2025-01-29 15:45:11.287][response][INFO] (get_org_user_mini_details) GET /api/organizations/<org_id>/users/mini-details => 200 OK
[2025-01-29 15:45:11.288][response][INFO] (get_groups) GET /api/organizations/<org_id>/groups => 200 OK
[2025-01-29 15:45:11.304][response][INFO] (get_org_collections_details) GET /api/organizations/<org_id>/collections/details => 200 OK
[2025-01-29 15:45:19.574][request][INFO] PUT /api/organizations/d09fb8b4-29e9-4cf8-af62-f92f7fc3d4bb/collections/1b052b32-15ba-4767-8af2-7c48c533e780
[2025-01-29 15:45:19.608][response][INFO] (put_organization_collection_update) PUT /api/organizations/<org_id>/collections/<col_id> => 200 OK
[2025-01-29 15:45:29.974][request][INFO] GET /api/organizations/d09fb8b4-29e9-4cf8-af62-f92f7fc3d4bb/groups
[2025-01-29 15:45:29.978][response][INFO] (get_groups) GET /api/organizations/<org_id>/groups => 200 OK
[2025-01-29 15:45:30.013][request][INFO] GET /api/organizations/d09fb8b4-29e9-4cf8-af62-f92f7fc3d4bb/users/mini-details
[2025-01-29 15:45:30.017][response][INFO] (get_org_user_mini_details) GET /api/organizations/<org_id>/users/mini-details => 200 OK
[2025-01-29 15:45:30.051][request][INFO] GET /api/organizations/d09fb8b4-29e9-4cf8-af62-f92f7fc3d4bb/collections/details
[2025-01-29 15:45:30.074][response][INFO] (get_org_collections_details) GET /api/organizations/<org_id>/collections/details => 200 OK
[2025-01-29 15:45:34.031][request][INFO] PUT /api/organizations/d09fb8b4-29e9-4cf8-af62-f92f7fc3d4bb/collections/1b052b32-15ba-4767-8af2-7c48c533e780
[2025-01-29 15:45:34.061][response][INFO] (put_organization_collection_update) PUT /api/organizations/<org_id>/collections/<col_id> => 200 OK
No event log was found.
Additional Context
No response
@sbdiun commented on GitHub:
Hello,
We have set up an organization in which we create main collections for individual teams, to which the team then has editing rights.
So that we (IT Service) do not have to create permanent collections and modify access for all teams, we would like to define one or more members of each team as managers who will then manage access to the collection.
However, not everyone from the team should be given management rights just because they are allowed to create and delete items in it.
Is there a way to do this?
The manager should also be allowed to create new (sub)collections.
However, he is currently not allowed to do this, but as an administrator he has too many rights, he should not be allowed to access collections from other teams. But I think this will be fixed by bug #5489, right?
@BlackDex commented on GitHub:
I think it works as expected.
The main reason here is that we want to try to keep compatible with the previous way of working where managers are able to manage collections and edit/delete ciphers.
So, if the user you are setting this for is a manger or higher, they will always get
can managerights instead ofcan edit.A normal user will get
can editrights.@stefan0xC commented on GitHub:
Why don't you setup separate Organizations for each team? That way you could have the manager be Administrators for their team without them having access to other teams and they can also control who has access to what in their Organization.
It allows managers to create new collections yes and unless you give an manager access to all collections, they should only be able to change (and see) the collections they have been given full write access to (where
Can editautomatically impliesCan Managefor Manager / Custom users).@stefan0xC commented on GitHub:
We currently use the Custom role as a placeholder for the deprecated (i.e. removed) Manager role. We don't yet have support for custom permissions. If they were implemented we could probably also get rid of this hack (cf. #5219).
@sbdiun commented on GitHub:
Ok, then we'll probably go that way.
One more question: The custom role implies that you can configure something, for example, could the right to create collections be restricted?
Where can you set the permissions in Vaultwarden, or is that a misunderstanding on my part?
@sbdiun commented on GitHub:
In any case, thank you very much for your answers
:-)
@sbdiun commented on GitHub:
I think I found the answer on this Bitwarden help page, but in a strange way:
The German version contains an English comment announcing exactly that in a later version. On the original page, the comment is missing.
https://bitwarden.com/de-de/help/collection-management/#collection-management-settings
“Collection management settings will be available for self-hosted Bitwarden servers in a subsequent release.”
Is there any hope that you can take it over?
@BlackDex commented on GitHub:
That has nothing to do with the way how Vaultwarden works right now.
The main reason Vaultwarden works as currently is the case is because we were stuck on web-vault v2024.6.x which was very old. To support the newer web-vault we needed a way to either mimic the manager role in an easy way, or change everything regarding the whole custom roles which has a great impact and needs very good testing.
That kind of change will take a much longer to fix, since we check on several places now if someone is a manger, admin or owner to be allowed to handle special endpoints. Switching to the more fine grained custom role needs careful testing and changing these permission checks.
So, until someone (me or someone else) is going to start on that, this hackisch way of mimicking the old manager role will stay as-is.
@BlackDex commented on GitHub:
moving this as not planned right now to discussions Ideas.