mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-05-06 19:38:34 -05:00
Import data (Firefox (csv)) not using "timePasswordChanged" #4889
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 @3ftomi on GitHub (Apr 12, 2022).
Subject of the issue
Exported login credentials from Firefox (latest:99) to .csv. In the .csv there is a row named "timePasswordChanged".
I supposed this field used to the "Updated" time field in Vaultwarden. Unfortunately I've faced that all Items have the same "Updated" time which is the time when the importing processed and not the original time (from the .csv) when a login changed.
This date and time are important to know how old it is. Maybe needed to change. Or if there is multiple instances which one is the newer.
Deployment environment
Install method: Docker image (QNAP, Container Station)
Clients used: web vault
Reverse proxy and version: QNAP QTS 5.0.0.1986 Builtin Reverse Proxy
MySQL/MariaDB or PostgreSQL version: MariaDB 5.5.68
Other relevant details:
Steps to reproduce
In Firefox > about:logins > upper right corner three dots menu > Export logins... > created logins.csv file
In Vaultwarden web vault > Tools menu > Import data > Firefox (csv) > Import data
Expected behaviour
In My vault > Item > "Updated:" time use the time when last changed (from logins.csv "timePasswordChanged" field)
Actual behaviour
In My vault > Item > "Updated:" time now showing the time when import taken.
Troubleshooting data
@BlackDex commented on GitHub (Apr 12, 2022):
That information is not sent by the clients and thus not something we can use or implement.
Also, this is something which is specifically build into the clients, which the Vaultwarden team does not maintain.
I would suggest to check if this also happens on vault.bitwarden.com (which i think it is) and then post a feature request here: https://community.bitwarden.com/c/feature-requests/5