The 1Password Community forums are in read-only mode from Jan 28th - Feb 4th, 2025. Find out more.

Can you please store username histories?

lmeyn
lmeyn
Community Member

I was registering an updated credit card online and when 1Password asked if I wanted to update the entry, it updated my login information and not my credit card info. Probably a dumb mistake on my part, but my login username and password were overwritten with my credit card number. I only found this out next time I tried to login. I could recover my old password, but not my username. Fortunately, I was able to login in using security questions, but it would be nice if 1Password had a username history. This might happen pretty often soon, as banks will be issuing millions of updated cards with new chips before the end of the year.


1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided
Referrer: forum-search:username history

Comments

  • littlebobbytables
    littlebobbytables
    1Password Alumni

    Greetings @lmeyn,

    So you were logged into an online retailers portal or a form with your bank and you were updating credit card details. I'm guessing the form was asking for the usual card-like information such as long number, expiry data etc. and 1Password asked if you wanted to update a Login item?

    Can I ask the following please.

    1. What version of 1Password are you running?
    2. What is your preferred browser and the version of that browser?
    3. What version of the 1Password extension is installed?

    Besides your request I would ideally hope we don't offer to save if we think we're looking at a credit card so that is something I would also want to address. That's why I'm asking the questions, to help pin down the issue.

    Now I was recently testing something and my finding was we didn't touch the username field even though I was instructing 1Password to update an existing Login item. Again, this might be something that the questions help to explain.

    Just for now, should anything like this happen again my recommendation would be the following approach.

    1. Backup your vault (with the lost username) using the File > Backup option in 1Password.
    2. This should open up 1Password's preferences in the Backup tab.
    3. Select a backup made just prior to the incident and click the now enabled Restore button.
    4. Follow the steps provided by 1Password.
    5. One you restart, find the Login item and make a note of the real username.
    6. Open 1Password's preferences and switch to the Backup tab.
    7. Now restore the newest backup, the one you made in step 1.
    8. Edit the Login item to correct the username using the information gathered in step 5.
    9. Restore sync if you previously had it set up.

    Now there are a few steps in there but they can be completed relatively easily and allows you to avoid recovering the account using whatever functionality the site in question has. I am sorry yo've had to reach out to us and hopefully we can better understand how this happened so that it doesn't going forward.

  • lmeyn
    lmeyn
    Community Member

    I've been staying pretty up-to-date with 1Password releases. I'm currently using 5.4 on the Mac under El Capitain and Safari 9.0. However, the overwriting of the username probably occurred with the immediately previous versions of 1Password and it's Safari extension. As I mentioned, I didn't notice the problem right away, so I wasn't using yesterday's release of 1Password at the time.

  • littlebobbytables
    littlebobbytables
    1Password Alumni

    Hello @lmeyn,

    Please do keep us updated should you experience anything like this again. As I say, we shouldn't be touching the username field as that is something that almost never changes - it's quite rare for a site to allow you to do so (unless they use your email address to authenticate that is). Still, we don't want to be touching the username without good cause. Should it happen again, and if you're comfortable in doing so, knowing the site it happened on should allow us to test and use the site as an example of this bad behaviour that needs corrected.

This discussion has been closed.