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 situation where the password is messed up and I don't know what it is. So I have to do a password reset. Because of long-standing issues in this area, I adopted the practice of saving existing passwords in a text editor and putting new ones there. I cannot tell you how many times I have to resort to those extra steps to save the day, as the automated features of 1P just fail. The net result is all the "helpfulness" results in unnecessary password reset requests with websites. Could you please simplify this and either get all the unwanted helpfulness out of the way or make it just work? 1Password Version: 7.9.1 Extension Version: 2.1.4 OS Version: 10.15.7

Hey jasimon9 , You didn't quite explain what goes wrong in your process and what can/should be improved, so I'll just describe the flow of things and include some key points and helpful notes that you might find useful. Get to the website you want to change your password for and log into your account. Get to the "Change Password" form. Let 1Password autofill your current/old password. In the "New Password" field, 1Password will usually show up on its own and suggest a new strong password. If you click and select the suggested password, 1Password will autofill it into the "New Password" and "Confirm new password" fields, and will ask you if you'd like to update your existing login entry with this new password. Confirm and update it. The login item entry will now contain the new password. Send the form on the page and make sure the website accepts the new password as well. Now, in some cases, the website will not accept the new password because it doesn't comply with the website's requirements. In that case, stay on the page and generate your own new password, like so: Click the 1Password extension icon in your browser's toolbar to open it. Click the grey key icon to reach the generator. Change the password's type from "Smart Password" to "Random Password" and adjust the recipe to comply with the website's requirements (length, digits, symbols etc). Autofill the password you generated. 1Password will autofill it and show you the update prompt again - confirm and update your login entry with the newer password. Send the form on the website and make sure that it accepts your new password. You can repeat these steps for as many times as you need until you get the website to accept your new password. If you ever need your old/original password back, you can recover it like so: https://support.1password.com/item-history/ In case you need to recover a password you generated in the generator, get to the generator and click the "Generator History" button at the bottom. These failsafes are there to ensure you will never lose access to your account and will always be able to recover the required password, so no need to use a text editor and copy-paste passwords. I hope you'll find this helpful. If you have specific actions or flows you'd like to point out for us to improve, please describe an example and how you'd improve it. :)

I understand that following specific procedures work. However, there are other procedures that are problematic. I seem to be able to find such procedures. Here is an example, which is not for changing passwords, as I was originally questioning about, but nevertheless shows issues. Create a login for a new website. In the password field, there are two choices presented: (1) suggested password; (2) save in 1P. If you click "save in 1P". It is not clear which of these choices I should take. When I save in 1P, it seems to save a different password, as if it is generating a new one. It would be best if the next time this happens, I take note of every single step and all the rework that I needed to finally get it right.

Hey jasimon9 , You can test things on our test website: https://fill.dev/form/registration-simple The "Save in 1Password" button will save all fields that were filled on the page as they are. If some fields are still empty, don't click the "Save in 1Password" button yet. Only click that button when all required fields are filled in. If you click the suggested password that 1Password offers, it will automatically tigger the save prompt so you can save that new password and won't lose it, but if you prefer to type in your own password and click the "Save in 1Password" button, make sure to click that button only when you're done filling all the fields on the page.

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,

Hey jasimon9 , I don't quite understand what the issue is with the example scenario and screenshot you provided. 1Password seems to be working correctly and doing its job here. If you sign up to a new website, 1Password will suggest a new password for you to sign up with. When you select that new password, it will trigger the save prompt and save the entire page for you (including the username and any other field that is filled), creating a new working login for you to use the next time you try to log into the website. You are not supposed to know or remember what the new password is because that's not interesting. That's not important. That is why 1Password was invented. Using the clipboard is not a great security practice and is one we try to avoid. The clipboard is not a secure space to store passwords in (even if only for a moment), so 1Password bypasses all that and saves what you need for you. If you ever find yourself in a situation where you did not save the password for some reason, you can still recover it in the generator's history as I mentioned in my previous reply. You will never be locked out of your account or lost without the password that you autofilled, we have failsafes that prevents it such as the generator's history. 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. That scenario is not possible unless the website does some javascript voodoo magic in the password field that changes the input you type in it. If the password field is empty and you click the "Save in 1Password" button, 1Password will show the save prompt and will have an empty password field in the new login item you create. If there was already something typed into the password field and you click on "Save in 1Password" (but you do NOT click on the suggested password), then 1Password will save whatever is typed into that field. The biggest point of interest here is that the "Save in 1Password" button and the strong suggested password are two separate functions that do different things, do not expect them to perform the same action. The Save in 1Password button will save whatever is filled into the fields already but will not add anything new to any field - it will not fill the suggested password it shows you. The strong suggested password option will overwrite whatever is in the password field and will autofill it with the new suggested password it showed you, then trigger the save prompt with that new password in it. I hope that clarifies things a bit better. If you encounter a website that is publicly accessible where you can reproduce a specific scenario where you're having troubles, please provide us the link here with an exact step-by-step description of your actions and clicks so that we can replicate it and follow up on it. : As I mentioned previously, you can use this website to do some testing: https://fill.dev/form/registration-simple

Trouble changing passwords | 1Password Community

ag_chantelle
1Password Team
4 years ago
You are most welcome, jasimon9 :smile:
jasimon9
New Contributor
4 years ago
Thanks for the explanation.
ag_chantelle
1Password Team
4 years ago
jasimon9

I see that my colleague Nhat has replied to your email. To avoid duplication, and to keep the conversation in one place, I'd suggest replying to him there.

To answer your last question here, the difference you're seeing are two different versions of 1Password for your browser. The version in Chrome is our newest standalone 1Password web extension with integrated features. The one you have in Safari is an App Extension that automatically comes built in with the desktop app for Mac - so the features will vary slightly. We are working to align these when we release 1Password 8 for Mac alongside 1Password for Safari later this year, so you can expect more consistency there.
jasimon9
New Contributor
4 years ago
Re the question about why secondary logins are created, when you say "continue there", I assume you mean that I will get an email reply (which I have not yet) and to reply to that email.

Do you have any idea why Safari does not give the choices that Chrome does on the right click?
ag_chantelle
1Password Team
4 years ago
Thanks jasimon9. I was able to locate your ticket. Let's continue the conversation there.

ref: NAB-32183-429
jasimon9
New Contributor
4 years ago
I tried right clicking on the 1P icon in the browser toolbar. In the dropdown the only choices are "Manage Extension" and "Customize Toolbar". Having had similar issues before with Safari not acting properly, I loaded Chrome, and the followed your steps. This time it did have Help > Collect Page Structure. So I did that .

I am again wondering why Chrome works as you would expect, where Safari does not.
ag_chantelle
1Password Team
4 years ago
jasimon9

Since the root domain of the site is the same on both URLs, it should not matter. It appears that the change password page sits behind a paying account, which we don't have access to. If you don't mind, I'd like to ask you to collect some page details for us to test:

On the page exhibiting the behaviour, right click the 1Password icon in your browser toolbar.

Click Help and choose Collect Page Structure.

1Password will save a .json file to your "Downloads" folder.

Send the downloaded .json file to us at support+x@1password.com with a link to our current discussion.

One of our extensions team members will have a look and let you know what we find.
jasimon9
New Contributor
4 years ago
I mean 1P did not update it in the login.

I was not given the choice to update the old one. It created a new one. My theory is that because the URL was different, 1P did not recognize that it could be an update. One URL was https://www.sitepoint.com and the other was https://www.sitepoint.com/premium/
Former Member
4 years ago
jasimon9:

But now I don't know what the password is because I did not copy it somewhere, and 1P did not update it.

When you say "did not update it", do you mean on the website?

1P asks to update or save the new password and I do so.

You do so meaning you chose to update the existing item or to create a new one? What option did you choose in the popup window? Because it sounds like you chose to create a new item instead of updating the existing one.
jasimon9
New Contributor
4 years ago
I just ran into another sequence that makes it a lot of extra work.

Attempt to login to website. URL has a directory, such as www.exmaple.com/premium/

Site tells me that they upgraded their passwords and I have to create a new one.

I use 1P to generate a new password.

1P asks to update or save the new password and I do so.

However, instead of updating the existing login, it creates a new one but with the URL not having /premium.

The next result is that I now have two logins. One has the old username, old password, and old URL. The new one is missing the username, has the new password, and a new URL. Now I have to work to combine the proper info back into a single login.

I have also noticed lately a lot of cases where the username is not being saved, or even the site name not being saved. Again rework to fix these to combine the information back together.

Forum Discussion

Trouble changing passwords

Recent Discussions

2 Factor Logon

Need help exporting

How to search for a specific string of text?

Passkeys in a compromised account

[Bug] Editing item website field goes blank