1passwordX misfills values in https://*.1password.com/signin

kv3
kv3
Community Member

(yep! It does :-))
I have two 1password accounts, one corp, and one personal. For convenience, I have equivalent entries, in separate vaults (not the core issue though), and the look as:

And the other is similar, with different credentials (email address, secret key, password). It does go to a different corp specific url, but I get the same behaviour.

However, and probably because of ordering, I notice that when i try to log into my corporate account, it still fills in the secret key from my personal account, which is rather what I didn't expect.

Known issue?


1Password Version: 7.8.4 (70804003)
Extension Version: 2.0.1
OS Version: Firefox 88.0.1
Sync Type: my.1password.com

Comments

  • kv3
    kv3
    Community Member

    The problem is repeatable on other browsers as well, safari, brave, ...

  • ag_yaron
    ag_yaron
    1Password Alumni
    edited June 2021

    Hey @kv3 ,

    If you've duplicated one of these items and just edited out the username, password and secret key fields, then you will experience this issue because the secret key field is being autofilled from the login entry's "Saved Form Details" section and not from the visible field you see in your screenshot.

    Please try this on the login entry that autofills the wrong secret key:

    1. Open the 1Password desktop app on your Mac.
    2. Select the wrongly autofilled login entry and click on "Edit" to enter edit mode.
    3. Scroll down to the bottom of its details and click on "View Saved Form Details".
    4. Reveal the secret key field and check if it is the correct secret key or if it is the other account's key and edit it accordingly.
    5. Click "Save" to save your changes and test autofilling now.
  • kv3
    kv3
    Community Member

    @ag_yaron
    THank you, yes, I see it now and it is working as I woudl expect, thanks,

    I see how I screwed up then,

    Kannan

  • ag_yaron
    ag_yaron
    1Password Alumni

    I'm glad to hear everything is working well now :chuffed:

This discussion has been closed.