mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2025-12-10 17:23:04 +03:00
Cannot nest collections using 'Password Manager' interface #397
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 @RBM1R on GitHub.
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
Steps To Reproduce
Expected Result
The full collections list to choose from in order to set the current collection's parent node.
Actual Result
In case of a new collection, only 'no collection' option is available.
In case of an existing collection, only 'no collection' and the current parent collection options are available.
Screenshots or Videos
No response
Logs
No response
Additional Context
The same workflow is available in 'Admin console' interface, but that is working.
Host/Server Operating System
Linux
Operating System Version
RHEL 8.6
Deployment method
Official Container Image
Custom deployment method
No response
Vaultwarden Build Version
1.32.0
Clients
Web Vault
Client Version
2024.6.2b
@RBM1R commented on GitHub:
Thank you for your quick reply.
I went a bit further down the rabbit hole, and I found that Bitwarden itself made changes around access control during the last months:
Unfortunately I don't have access to a Bitwarden enterprise license (which is needed to run self-hosted organizations), or I'd be happy to provide better insight about those differences.
@BlackDex commented on GitHub:
That will not help. As mentioned it still is an issue with v2024.8.0.
You can check it on vault.bitwarden.com if you want.
Vaultwarden has v2024.6.2 currently, and we can't really update to a newer version a.t.m. because of all the role/collection changes they made. We need changes and migrations for this first on the server side.
@BlackDex commented on GitHub:
This seems to be a client issue, and collections are able to be set in a correct way via the admin console.
As far as i can tell, this is still an issue even with v2024.8.0.