mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #3249] Read Only rights issue with Groups generating trash entry on user vault #1510
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#1510
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 (Feb 16, 2023).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/3249
Subject of the issue
Read Only rights issue with Groups generating trash entry on user vault (with the groups beta feature enabled).
Deployment environment
Install method: Custom Built with docker with last #3108 Merge (same issue with docker vaultwarden/server:testing )
Clients used: web vault
Reverse proxy and version: No
MySQL/MariaDB or PostgreSQL version: MariaDB 10.10.2 , Same issue with Sqlite
Environment settings:
Steps to reproduce
4.1. Give permission of that collection "C" to the group "G" with Read Only access
4.2. Assign the user "U" to the group "G"
4.3. Make sure that the user "U" does not have direct permission on the collection "C". In other words: the permission should be configured via the group only!
5.1. Add a new entry to the collection "C", "C" is shown even if the group is in RO access
5.2 Save the entry -> Error message
No rights to modify the collection5.3 A blanck entry is created automatically with nothing inside in the user "U" vault (see screenshot)
Expected behaviour
User can't select the collection "C" with rights read only (assign by a group)
This is already working for rights directly applied on user (user can't select collection with read only access)
Actual behaviour
User "U" can select a collection "C" with rights read only (assign by a group) and create automatically a trash entry in his personnal vault
Troubleshooting data
Trash entry created :

Collection available list when creating entry with rights applied on groups

Collection available list when creating entry with right applied directly to user (Expected behaviour with group)

@Misterbabou commented on GitHub (Feb 16, 2023):
I modified Steps to reproduce to explain the steps better
I made new tests with those changing variable :
1 - image: vaultwarden/server:testing (last available), and MariaDB 10.10.2
2- image: vaultwarden/server:testing (last available) and Sqlite
I have still the same issue with those additional tests.