Editing Password History List

Spaceman

Just curious,



Is there a way to delete items from the Password History list? Today, while updating a password, I ended up with 4 separate history entries for a particular password. The last three are the same password. It is not a big deal but it would be nice to delete the other three duplicates.





John

thightower

Hi John,



It has been a really long time since I saw this question asked. If the developers have not changed it recently then No there is not anyway to delete the history. They consider this a filing cabinet for backups of old passwords.



Having said that you could try duplicating the login and see if it caries over the history. Make sure the new login does contain the password and username before you delete the original one. That is if it solves the history problem.



My OCD gets the best of me at time and I do spring cleaning to. But for the most part I just leave the history alone. Unless it's one of those days when it hits hyper drive. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=':)' />



Sorry I couldn't give a better answer I would have checked for you but I'm mobile at the moment.

khad

As a solution for "Password History removal" item duplication will not fit the bill. This has been the source of much debate since some folks absolutely insist that "a duplicate is a freaking duplicate!" Thus the inclusion of the password history. Right now, the only way to "remove" the Password History is to simply create a new item. Note that you can also do this by "replacing" your current item during a manual save:



1. Enter your username and password, but DO NOT submit the form. (You can do this by holding down the Option key when selecting the login from the 1P toolbar button in your browser)

2. Click the 1Password button in your browser's toolbar, and choose Save Login.

3. Change the Action field from "Create New Login" to "Replace <login-name>" to replace the existing Login item.

4. Click the Save button.



The new Login should not contain the original Password History.



Even this is a bit of a "hack." When we consider consolidating the "update" and "replace" mechanisms, this will be very undesirable behavior. Until then, though…please let me know how it turns out.



Of course, the Password History does no harm hanging out there. The Password History section is intended to be a safety net, so we recommend leaving it intact.



If anyone knows about an abundance of Password History cluttering up a data file, you can be sure that we at Agile do (with all the testing we constantly perform)! There are too many to worry about. I treat it like my Gmail archive. I never look at it, but I can search it if I ever need to. And I have certainly needed to once or twice after some login testing shenanigans. Saved my bacon on more than one occasion. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_wink.png' class='bbc_emoticon' alt=';-)' />



Please let me know if there is anything else I can help with.



Cheers,

Spaceman

[quote name='khad' timestamp='1304970190' post='26648']

As a solution for "Password History removal" item duplication will not fit the bill. This has been the source of much debate since some folks absolutely insist that "a duplicate is a freaking duplicate!" Thus the inclusion of the password history. Right now, the only way to "remove" the Password History is to simply create a new item. Note that you can also do this by "replacing" your current item during a manual save:



1. Enter your username and password, but DO NOT submit the form. (You can do this by holding down the Option key when selecting the login from the 1P toolbar button in your browser)

2. Click the 1Password button in your browser's toolbar, and choose Save Login.

3. Change the Action field from "Create New Login" to "Replace <login-name>" to replace the existing Login item.

4. Click the Save button.



The new Login should not contain the original Password History.



Even this is a bit of a "hack." When we consider consolidating the "update" and "replace" mechanisms, this will be very undesirable behavior. Until then, though…please let me know how it turns out.



Of course, the Password History does no harm hanging out there. The Password History section is intended to be a safety net, so we recommend leaving it intact.



If anyone knows about an abundance of Password History cluttering up a data file, you can be sure that we at Agile do (with all the testing we constantly perform)! There are too many to worry about. I treat it like my Gmail archive. I never look at it, but I can search it if I ever need to. And I have certainly needed to once or twice after some login testing shenanigans. Saved my bacon on more than one occasion. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_wink.png' class='bbc_emoticon' alt=';-)' />



Please let me know if there is anything else I can help with.



Cheers,

[/quote]





Thanks for the reply. I kind of figured that would be the answer. Just to be clear, I did not want to delete the entire history for the password, just the 3 of the 4 duplicates that got generated about a minute apart. As I originally said, this is not big deal. Just thought I would clean it up if possible.



Regards,



John

khad

Thanks for the update, John. I'm glad it isn't too big of an inconvenience, but it is something we are looking to improve in the future.