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.
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
Originally created by @3ftomi on GitHub (Apr 12, 2022).
<!--
# ###
NOTE: Please update to the latest version of vaultwarden before reporting an issue!
This saves you and us a lot of time and troubleshooting.
See:
* https://github.com/dani-garcia/vaultwarden/issues/1180
* https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image
# ###
-->
<!--
Please fill out the following template to make solving your problem easier and faster for us.
This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them.
Remember to hide/redact personal or confidential information,
such as passwords, IP addresses, and DNS names as appropriate.
-->
### Subject of the issue
<!-- Describe your issue here. -->
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
<!--
=========================================================================================
Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab.
That will auto-generate most of the info requested in this section.
=========================================================================================
-->
* vaultwarden version: 1.24.0
<!-- How the server was installed: Docker image, OS package, built from source, etc. -->
* 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
<!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults)
and how did you start vaultwarden? -->
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
<!-- Share any log files, screenshots, or other relevant troubleshooting data -->
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.
@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
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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