mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #4886] Importing from Proton Pass Export Does Not Import Usernames #2014
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#2014
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 @mzrimsek on GitHub (Aug 23, 2024).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/4886
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
I expect the Username field to be populated
Actual Result
The username field is empty.
Screenshots or Videos
No response
Logs
No response
Additional Context
It seems that the import isn't perfect with custom fields but most all of the other normal fields have imported as expected.
I suspect the issue is Proton Pass was recently updated to be able to have both a Username and Email in a single login entry. Without knowing what the old JSON looked like, I'd venture a guess the issue is the new output is a slightly different to export both fields and the username field isn't mapping correctly in the import.
Host/Server Operating System
Linux
Operating System Version
Ubuntu 20.04
Deployment method
Official Container Image
Custom deployment method
No response
Vaultwarden Build Version
v1.32.0
Clients
Web Vault
Client Version
v2024.6.2b
@BlackDex commented on GitHub (Aug 23, 2024):
I'm afraid that isn't something we can fix. Imports are handled in the client side and then send to the server in an encrypted form.
It might be that a newer client has fixed this already, but we currently can't update to a newer version yet.
I would suggest to check if you can export it in a different format and use that to import.
@BlackDex commented on GitHub (Aug 23, 2024):
Looks like they fixed it, though not sure.
https://github.com/bitwarden/clients/pull/9889
https://github.com/bitwarden/clients/pull/10471
But again, we can't update to a web-vault which has these fixes because of some technical dept we have to support these new web-vault versions.
Since this isn't specifically a Vaultwarden issue we can fix other then updating the web-vault I'm going to move this to a discussion.