mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
Duplicate collection on import #1870
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 @bundfeg on GitHub (Mar 5, 2024).
Subject of the issue
Import into collection duplicates this collection
Deployment environment
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: DOMAIN, SENDS_ALLOWED, SIGNUPS_ALLOWED, SIGNUPS_DOMAINS_WHITELIST, ORG_CREATION_USERS, ADMIN_TOKEN, INVITATION_ORG_NAME
Install method: docker image
Clients used:
web vault
Steps to reproduce
Given:
Test-Collection with Old-Entry (collectionId=f9b42dca-8d96-4b86-b8bd-0198a8020c37)
Folder in Keepass with New-Entry
Export from Keepass 2
Entry:
Keepass 2 Entry - Data exchange - Export entry - Keepass XML 2.x -> entry.xml
Folder:
Group - Data exchange - Export group - Keepass XML 2.x -> folder.xml
Organization - Settings - Import data - Collection: Test-Collection - File format: KeePass2 (XML) - Select the import file: entry.xml - Import data -> "Data successfully imported" Login: 1; Collections: 1
Result: New Collection (ollectionId=90214cb8-4407-445e-836a-bd3f9e51a6e4) with single entry test-entry next to the existing old Test-Collection with Test-Entry (collectionId=f9b42dca-8d96-4b86-b8bd-0198a8020c37)
same with import of folder.xml
Expected behaviour
I would expect the entries from keepass to be added to the selected collection and no duplicate
Actual behaviour
collection is duplicated (same name, different id) and the entries from the import are in this new collection
Troubleshooting data
@BlackDex commented on GitHub (Mar 5, 2024):
I'm afraid we can't fix that. The server just receives encrypted data with no way for us to see names of collections or folders.
If the ID is different, then the client crested a new collection which the server then will create as requested.
@bundfeg commented on GitHub (Mar 5, 2024):
Ah, ok. I was using the website provided by the docker container. Where do I have to report this bug for the "client" you speak of?
@BlackDex commented on GitHub (Mar 5, 2024):
If it is a bug it might ask ready be reported at Bitwarden.
Which maintains all the clients.
@bundfeg commented on GitHub (Mar 5, 2024):
Thanks a lot :-)