It’s should showing the latest password not old one
i see it’s same on the website
I don’t know how the data got into this state, but the way that BW shows password history is that:
- The history date is when you changed the password.
- The password saved in history is the password you replaced, not your new password.
So from the information shown on your screen:
- On 2024/9/12 14:25, you replaced the password “…Gwv” with “…gNZ” (the current password in your record).
- On 2024/7/21 01:41 you replaced the password “…gNZ” with “…Gwv”
Do you have the Settings → Notifications → Ask to update existing login turned on? If you do, and somehow, the old password was entered on login, could you have updated the password with the old one unintentionally?
Because the automatic password saving doesn’t work in some cases, some people turn off “Ask to add login” and “Ask to update existing login”, and create/update the password explicitly using Bitwarden before entering the old password/new password into the password change form on the website. This way, changing the password in BW record is very explicit, and cannot be unintentionally done with a single click.
1 Like
Hello,
I’m probably in the same (or a similar) boat here.
On one site I can see that there are 3 passwords for the same account in total.
- the oldest pass1 seems to have been made on Oct 7th, at 10:09:12am
- the second oldest, pass2, seems to have been made on Nov 20th, at 8:25:58am
- and there’s the “active” one, pass 3
The correct one is pass3, I’ve confirmed that.
There are two issues:
- When logging in today, pass1 is autofilled instead of pass3! This did not happen in the last two weeks, that is I was always offered pass3. What might be the cause here?
- according to the password history, pass2 and pass3 seem to have occured at the same time, how is this possible?
Running Firefox desktop (latest) with BW extension 2024.11.2 at the moment.
Hello @cosmos ,
As for your 2nd question, you should read the data like this:
- pass1 is replaced by pass2 on Oct 7
- pass2 is replaced by pass3 on Nov 20
i.e. the date indicates when the password shown is replaced, not created.
As for 1, it sounds like a bug. You can try to duplicate it on the test page: Test Form - KeePass . You can create a password “1”, change it to “12”, and change it to “123”, and autofill the page to see how many characters are shown in the password field. If you can duplicate it, you can file the bug at:
If you can’ t duplicate it (I can’t), there might be other explanations:
- Is your browser’s password manager autofill function turned off?
- Do you have more than one BW entries matching with the page?
Hello @Neuron5569
thanks for the informative post. Appreciate the explanation regarding the displayed dates. Addressing BW devs, personally I understand that if a date exists next to something, it’s its “birth” date and not its “decommissioned” one. A small text could be added perhaps?
I could not reproduce the issue on the Keepass date. Closest I came to a bug there is that I could not get the BW extension to prompt in order to save the new pass, after entering it on the form… Works at some times, does not at others. But I can not reproduce the issue on demand.
As for your questions:
- No autofill is enabled and the default setting is to auto-display passes for new credentials
- I’ve got another one. But, the user name in those is different (pass as well); so when autofill takes place I’m certain I’m on the right credentials.
Still can’t understand why it decided (and still does) to work lilke that, whereas it worked like a charm for the last 10 days…
- Just to make sure, I would turn off FF’s password manager settings, as suggested by BW here:
Also, delete all your already imported passwords (if any) in “Saved passwords”.
-
If that wasn’t the problem, I’d consider changing the password on the website to get around this problem.
-
As for why this issue only occurred now and not in the last 10 days, you might want to check Bitwarden’s last update date. You can do this by pressing Ctrl-Shift-A (or by entering “about:addons” in the URL), clicking the “…” next to Bitwarden, selecting “Manage,” and then checking the “Last updated” information. I didn’t suggest this earlier because version 11.2 was released more than 10 days ago, making it seem unlikely. The autofill function is part of the client-side code, so Bitwarden couldn’t have made any changes to it unless the client was updated.
- FF password settings have been disabled from the very first day of installing BW and FF passwords have been deleted as well
- I know, question is why this happens and/or whether it hides some other, more significant problem
- It was updated on December 2nd. Therefore, the fact that I have had the exact same version for the last two weeks makes the issue rather unexpected.
For the record, it was able to reproduce it today.
EDIT: Tried to see what happens on my Firefox on Android. The issue did not appear there (even though bitwarden failed to fill in the login and I had to find it in the vault and copy paste it manually. It’s crazy just how much of the Firefox’ native password functionality is still missing from BW…).
Hi Cosmos,
Sorry this didn’t get resolved for you. Besides other ideas already proposed, here are two more:
- The 2024.12.0 (with UI refresh) has been dropped. It can’t be more than a week away before it appears on the FF extension store.
- It’s easy to downgrade FF extension. Install it from the page: Bitwarden Password Manager version history - 25 versions – Add-ons for Firefox (en-US) and then turn the auto-update off.
If it is a bug, though, never filing means it may not get fixed…
Your screenshots above are not from 2024.11.2, they are from 2024.12.0 (or from a Chrome browser running the beta release version 2024.11.999 or 2024.11.9991).
Please clarify what in version of the extension you are experiencing the problem in.
On the KeePass Test form?
Typing this on mobile, so please bear with the mistakes and poor appearance.
- The screenshots I posted were taken from the web vault and not from the toolbar.
- Error was reproduced on the hpe site (where the issue appears).
Additional info: the hpe site is one of those where logging in is a two-step process. I had had autofill enabled when the issue appeared.
Today I disabled autofill. After doing so I noticed that the correct (latest saved) pass was inserted.
I was in a hurry, so I could not retry this. However, it feels that if it is reproducible I the sense that it appears on this site with autofill on and doesn’t with autofill disabled, it might be something to be eradicated (bug).
What do you mean by “Autofill”? Bitwarden has about five different ways of enabling autofill, or are you talking about your Firefox browser’s native autofill functionality?
Do you mean hpe.com? If so, I have tested the sign-in form, and was unable to reproduce your problem (although my tests were in Chrome, and I don’t know whether my “autofill” is enabled or disabled according to your definition of these terms).
I’m referring to the BW functionality, essentially when this checkbox is togggled on:
Yes, I’m referring to the authorization link by hpe.com that you will be taken upon trying to visit https://support.hpe.com/connect/s/viewcases
Made some tests with edge with the new design BW toolbar. Could not reproduce the issue as well.
Then tried the following: as I’ve described, I had another account matching hpe.com, albeit a different URL. I deleted that account temporarily in BW. By doing so, only one account left matching, the one with the 3 password in its history. Trying to login this time worked perfectly!
Thinking this might have something to do with the 2nd account, I restored it from trash, restarted firefox and … I still could not reproduce the issue.
So that’s about it, consider the case closed (even though I’ll never know what happened)
PS; Made the tests in this post or another system of mine, again with Firefox and BW… So it was not related to the specific installation at work.
For future reference, this method is called “autofill on page load”, or "automatic autofill.
Having enabled “autofill on page load” for the HPE site, I am unable to reproduce your issue with old passwords being autofilled, even on a Firefox browser. It is plausible that the second vault item in your browser extension was autofilling an old version of the password.
I’m glad that your situation appears to be resolved at this time.
Hopefully, the OP (@Brussels9059) is also no longer experiencing any problems since October.
Definitely not, IIRC I used the eye to check that it was indeed the oldest password from the account I intended to use.
Thank you all, for the time you’ve allocated to helping me out with this! 
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.