User-unfriendly and fragile workflow for updating passwords?
I'm using the 1password app on MacOS. I have a password stored there that I need to change. This password is associated to the site I'm using it on. I would like to keep the old password just in case, for example if I need it to update the client on another device, if the update fails because the password is too complex and I have to enter the old password again, whatever, I just don't want it to be instantly forgotten because I'm not yet totally sure I won't need it again. I thought that was handled by the archive, but that does not seem to be an option.
At first I created a new password with the same website indicator, now I duplicate it and edit the "original", then after some time I get rid of the copy.
Is there a better way?
My ideal workflow would be that if I edit (or call it "update" maybe) a password, the old version is archived and I can access it if needed. The archive would have some indication that "this version was active from xxxx-xx-xx to xxxx-xx-xx". I want some reassurance that things will not just disappear even if I replace them with a new version.
1Password Version: 7.9.10
Extension Version: Not Provided
OS Version: 13.3.1
Browser:_ Chrome
Referrer: forum-search:renew password
Comments
-
Hello @Lorens! 👋
Before I answer your question, I see that you're using an old and no longer supported version of 1Password and I recommend that you upgrade to the latest version: Upgrade to 1Password 8
There's no need to duplicate items before changing a password since 1Password already remembers your old passwords for you. After you change a password for a given website you can view old passwords that you've used on that website by hovering over the password field and then clicking View Password History:
If you're already using a 1Password membership then you can also view an item's history on 1Password.com: View and restore previous versions of items
Let me know if you have any questions. 🙂
-Dave
0 -
Thanks, indeed I did not see that. I was a bit surprised by the date shown, as it appears to be the date the password was deprecated and not the date it was created, but OK!
0 -
I'm happy that I was able to help. 🙂
-Dave
0
