1password 4 does not match/filter subdomains

admxnl

I have 2 logins each for different subdomains (e.g. subdomain1.domain.tld and subdomain2.domain.tld) but 1password does not filter them. It just offers both logins for each subdomain.

It would be nice to have an option to set the login only to respond for the specified subdomain.

DBrown

Does toggling the Lenient URL matching option (on the Logins tab of 1Password preferences) make any difference?

admxnl

It seems to solve my problem when I activate the Lenient URL matching option.

According to a previous discussion the activation should disable subdomain matching, so I guess this option is not working correctly?

svondutch

I have 2 logins each for different subdomains (e.g. subdomain1.domain.tld and subdomain2.domain.tld) but 1password does not filter them. It just offers both logins for each subdomain.

Correct. We display both Login items because they both match the domain.tld domain, but if your web browser is on subdomain2.domain.tlb then this Login item should appear at the top of the 1Password menu (above the other Login items that do not match your subdomain).

RichardPayne

@svondutch‌
Maybe you've considered this, but if not then maybe one for your infinitely expanding todo list:

Allow the user to enter partial urls and then only perform matching on the domain levels higher than the ones specified. For example:

Login 1
Url: example.com
Matches:
www.example.com
https://example.com
sub1.example.com
sub2.sub1.example.com
www.example.com/login
sub1.example.com/admin

Login 2
Url:
sub1.example.com

Matches:
sub1.example.com
sub2.sub1.example.com
https://sub1.example.com
sub1.example.com/login
sub1.example.com/admin

Does not match:
www.example.com
https://example.com
www.example.com/login
www.example.com/admin

Login 3
Url: sub1.example/login

Matches:
sub1.example.com
https://sub1.example.com
sub1.example.com/login
sub2.sub1.example.com/login

Does not match:
www.example.com
https://example.com
www.example.com/login
www.example.com/admin
sub1.example.com/admin
sub2.sub1.example.com

Basically, start at the TLD and work out in both directions.

I'd also consider change the Lenient Matching checkbox to the "Matching Rule" dropdown containing:

Single Match (same as current Lenient Matching off)
Lenient Multiple Matches (same as current Lenient Matching on)
Strict Multiple Matches (New scheme above)

svondutch

@RichardPayne for domain matching, we use Mozilla's public suffix list. Then we move some of your matching Logins to the top of the menu (primarily sub-domain matches, and your favorites). Those then appear above "Show X more items..."

RichardPayne

Using the public suffix list is fine for determining the starting point. What I was suggesting was that you allow the user to more tightly specify what will match.

admxnl

@RichardPayne I agree with more user control.

svondutch

@RichardPayne @admxnl Over the years, we have rewritten domain matching quite a few times, up to the point it was so complex that nobody (not even us ourselves) understood what it did.