Skip to main content
October 5, 2022
Question

Not matching Subdomains

  • October 5, 2022
  • 14 replies
  • 597 views

I have a set of logins that do not show up as suggestions when their sites match a subdomain.
You can see in the screenshot that I can search for a login with the website:

https://deploy-preview-1770--whoosh-staff.netlify.app/login

However, it does not show up automatically when I'm on the site:

https://deploy-preview-1837--whoosh-staff.netlify.app/login

Even though they differ only in their subdomain. Other sites seem to match correctly across subdomains. Is there something I should be doing differently?

14 replies

March 3, 2023

This thread was the first time I heard about this feature, and lucky me I am already running 8.10.0 (macOS). I changed all my subdomain logins to "Only fill on this exact domain" and restarted 1Password, but the + \ window hasn't changed, it still suggests everything from that parent domain, and not always in a well-sorted order either.

1Password Employee
March 6, 2023

Hi @BesieDai

Could you please let me know a little more about your setup?

Also, do the changes you've made affect the in-line menu from 1Password in your browser, but not Quick Access?

We'll be happy to troubleshoot with you. Thanks!

Ben

March 7, 2023

I'm using Firefox 110.0.1, with the 1P extension 2.6.0. I also explored this with Chrome 110.0.5481.177 (1P extension 2.7.0).

In Firefox, nothing is auto-suggested. I prefer to use ⌘ + \ instead of moving my hands to the arrow keys or mouse. And when I do bring up the 1P prompt, it's suggesting all the items for my parent domain in the wrong order.

In Chrome, there is a dropdown suggestion whenever the cursor is in a password field. And that dropdown seems to sort the most relevant one (the matching subdomain) at the top, with the others matching the parent domain below it. But as soon as I hit ⌘ + \, I get the wrongs ones suggested first.

And when that happens, I can't determine what the sorting order is, it's not alphabetical. The one almost always suggested first has a local ip as its primary website. So imagine this: I go to portainer.mydomain.com, open the 1Password shortcut, and not only does it first suggest the login for "MinIO Console", but the website shown in the display isn't even the one that should be matching the pattern.

April 17, 2023

I am also seeing problems with subdomain matching where I have two Okta accounts for work that are on different sub-domains, call them acme.okta.com and acme-cloud.okta.com. Both are configured with the new "only match this exact domain" setting.

What I have observed is:

On acme.okta.com I only get prompted with that exact login as expected. Verified in Firefox, Chrome, Safari, and 1p Quick Access

On acme-cloud.okta.com:
- in 1p Quick Access or Firefox I see both logins and acme.okta.com is the first option
- in Chrome or Safari I see both logins, but acme-cloud.okta.com is the first option
- if the acme.okta.com login is favorited in 1p (which is how I have it) then Chrome/Safari show it as the first option just like Firefox and 1p Quick Access do in either case
- in all these cases I expected that only the acme-cloud.okta.com login would be shown

1Password for Mac 8.10.4 (81004032)
1Password for Firefox 2.9.0
1Password for Chrome 2.9.0
1Password for Safari 2.9.0