mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2025-12-09 17:23:04 +03:00
Bug: Sub-collections created in one organization appear in another #20
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 @ktunda on GitHub.
Prerequisites
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, EMERGENCY_ACCESS_ALLOWED, PASSWORD_HINTS_ALLOWED, ADMIN_TOKEN, IP_HEADER, DISABLE_2FA_REMEMBER
Config:
Vaultwarden Build Version
v1.34.3
Deployment method
Official Container Image
Custom deployment method
Official Container Image
Reverse Proxy
Caddy 2.x
Host/Server Operating System
Linux
Operating System Version
Debian GNU/Linux 12 (bookworm)
Clients
Web Vault
Client Version
Latest Web Vault version bundled with Vaultwarden v1.34.3
Steps To Reproduce
Expected Result
The sub-collection created in "Neocom" should only appear inside the "Neocom" organization and not in "Trillion" or any other organization.
Actual Result
The sub-collection created in "Neocom" is also displayed inside the "Trillion" organization, even though it was not created there.
Logs
Screenshots or Videos
Additional Context
This behavior is consistent and replicable. It causes confusion in credential segregation between organizations and may lead to incorrect access management.
@BlackDex commented on GitHub:
You personal overview shows all items, collections etc...
That is how Bitwarden works.
Also, this is a client side item and nothing we can change on the server side.