Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
jasimon9
5 years agoSuper Contributor
Trouble changing passwords
I know you are trying to make 1P better and help with changing passwords. Yet your software needs improvement. I am continually running into situations where 1P is "trying too hard", and I get into a...
Former Member
5 years agoI can relate to every word from jasimon9. He described the issues very good. I don't have such issues with every password change, but from time to time. The changing of a password is the most fragile workflow you find in 1Password.
The main issue for me is that you have to change the password in 1Password before you actually change it on the website. If the website rejects the new password, you're often thrown back and need to enter the old password again, which can then only be found in the history, which gets real tedious, as soon as the password is rejected multiple times: which of the last passwords was the real old one? The last one? The next to last one? Or even the third? The history starts to get cluttered with passwords that were never active. It's also not clear if you will really get a valid new password according to the policy of the website, because you never see the new password. You cannot validate the password manually. I also tend to use a copy via clipboard to some notepad to "see" the new password. Which is a security risk of course. 1Password doesn't support me here good enough.
I recommend an update workflow in two steps. Instead of directly saving a new password, I propose the new password is saved to a temporary area, if I click on "save Login". Then I update the password on the website. I may need multiple loops until a new password is accepted. After the new password is actually accepted on the website, I click on a "commit password" function and commit the temporary area to the real password entry. If I abort the password changing, I do nothing or use some "abort password change" function to clear the temporary area.
An alternative to this could be "rollback password" function that pulls the last password from the history if the last change was only a few seconds ago and inserts it again as current password. I would use this to restore the password entry to the start, if a password was rejected and I have to do it all again. This should throw away and destroy the rejected password from the entry, which makes sense, because it was never active.