1PW saves different password than used to create account

UkuKawa

I have become quite untrusting of 1PW when creating a new account entry, including now 1PW 7.7. Specifically, the PW saved by 1PW is often not the PW used to create the new account entry.

Because of this reoccurring problem, I use 1PW to create a new PW, save that PW in TextEdit, and copy and paste that saved PW when creating the new account. After 1PW saves the new account record, frequently the PW in the 1PW entry is totally different, and edit is necessary to correct the entry.

Apparently not related to this problem, 1PW 7.7 camping on top of the Login userID and PW is quite annoying.

---

1Password Version: 1PW 7.7
Extension Version: 1PW 7.7
OS Version: OS X 15.7; Safari 14.0.1
Sync Type: 1PW
Referrer: forum-search:1PW saves different password than used to create account

ag_ana

Hi @UkuKawa!

Can you give us an example of a website where this is happening, so we can test it? Thank you!

UkuKawa

The last time this occurred was on twc.com just a few days ago. However, the situation was not simply creating a new 1PW entry. I had a twc.com account that I had not used for about 10 years and had no 1PW entry. The user name and PW for the account was an email address that was no longer active, and part of the process in correcting the account was changing the user name to a current email address and required changing the old PW to a new PW. My recollection is that it was after completing the process that I checked the 1PW saved PW with the saved TextEdit PW which were different. If it helps, 1PW has saved the following websites, with website 2 resulting with the same or similar tracking tracking information as website 3. I think I should change website to the same as website 2 and delete website 2 and website 3.

website: https://signin.att.com/dynamic/iamLRR/LrrController?IAM_OP=error&errorCode=902.2&appName=m10707

website 2: https://signin.att.com

website 3: https://signin.att.com/dynamic/iamLRR/LrrController?IAM_OP=login&appName=aaid_client&loginSuccessURL=https://oidc.idp.clogin.att.com/mga/sps/oauth/oauth20/authorize?nonce=TtTCrg1gXe&redirect_uri=https%3A%2F%2Fcaaid.att.com%2Fisam%2Fsps%2Foidc%2Frp%2Fconsumerfed%2Fredirect%2Faaidpartner&response_mode=form_post&alt_dest=https%253A%252F%252Fcaaid.att.com%252Fisam%252Fsps%252Fstatic%252FsigninRedirect.html&scope=openid&response_type=id_token&state=3JZuz3s0Ng&client_id=aaid_client

ag_ana

@UkuKawa:

Thank you for the additional information. I also forgot to ask you something else. You wrote:

Specifically, the PW saved by 1PW is often not the PW used to create the new account entry.

When you say that 1Password is not storing the right password in the field, and that it actually saves a different password, what exactly is it saving?

UkuKawa

By not storing the correct PW, that is the one used to create the entry, 1PW stores a PW what looks very like a 1PW generated PW, jumble of upper-case and lower-case letters, and a few numbers of a length similar to length 1PW generates. I don't recall if this last incident included special characters.

I don't very often make new 1PW entries, but I'd be surprised if it doesn't occur again. Next time I'll try document very carefully.

ag_ana

@UkuKawa:

Next time I'll try document very carefully.

That would be great, thank you. I have tried reproducing your issue but I could not get 1Password to store the wrong value, so if you find a way to consistently reproduce this on demand, by all means let us know and we will be happy to test the steps.