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...
jasimon9
5 years agoSuper Contributor
Here is yet another failing scenario: setting up a new user in postfix.
- when password field is arrived at, 1P suggests a password.
- If that is clicked on, the password fields are filled and a popup appears to update the postfix password. If you are not careful, you will update the postfix password. You don't want this to happen because you are not changing the postfix password so you have to be careful to click Cancel.
- Now the password is filled, but one does not know what it is. Previously whenever 1P filled, it would copy the newly generated pw to the clipboard. This no longer happens. So now you have a newly generated password that you don't have any information on.
Bottom line, 1P is getting in the way here, and not helping. The only solution for such a case is to ignore 1P. Generate a pw separately and save it in an editor and use it, and later update 1P with that pw. Lot's of extra steps. Don't either click on the suggested pw or the Save to 1P. Both of those will trigger a lot of rework.
Another scenario: an issue that I was experiencing before is that if you click Save in 1P, it saves a different pw than the suggested one. So now you have put the suggested pw into the website, and saved a different one in 1P. Again, rework required with the website to request another pw reset.
All of these mean that 1P pw set and change features have changed from a tools that just worked, to one that should be ignored,