Browser extension prompts unrelated logins to fill

For a specific website, I have one saved login in 1Password (and that website is also configured as a website in that saved login item). Yet, when I visit that website and need to log in, the browser extension prompts me for four different logins that have been saved in 1Password (1 being the right one, 3 being wrong/unrelated). How can I get the 1Password browser extension to stop prompting me for those 3 unrelated logins? Those 3 logins already don't have that specific website saved as website items in those saved logins, so I don't understand why it's prompting those 3 wrong/unrelated credentials on that specific website at all.


1Password Version: 1Password for Windows 8.10.58 (81058041)
Extension Version: 8.10.56.28
OS Version: Windows 11 24H2
Browser: Firefox 134.0.1

Comments

  • Hello @DVkUGgPR5VUh! 👋

    I'm sorry that you're seeing unrelated items being suggested for a certain website. Are you able to share the address for the website in question so that I can test this on my end?

    If you prefer not to share this on a public forum then you can send the website address to support+forum@1Password.com and include a link to this thread.

    Do not share your username and password, just the website address.

    -Dave

  • DVkUGgPR5VUh
    DVkUGgPR5VUh
    Community Member

    Hi Dave-

    The website is an internal company website that's in this format:
    https://subdomain.example.com

    The one relevant login includes a "website" item defined as:
    https://subdomain.example.com

    So it makes sense to me that the browser extension offers that login for filling.

    However, the other three irrelevant logins that the browser extension offers for filling on that website don't have that website defined as "website" items in those logins. They do have other websites saved, but not that one. This is what the "website" items are configured like on the irrelevant 3:

    https://subdomain2.example.com
    ...
    https://subdomain7.example.com

    https://subdomain2.example.com (different username than above + MFA)

    https://subdomain2.example.com/dir1/dir2/...

    None of the irrelevant logins have
    https://subdomain.example.com
    configured as a "website".

    (Unlike my examples here, the actual sites don't have a text string in common among them, like "subdomain" being present in both "subdomain" and "subdomain2".)