Subdomain sensitive autocomplete suggestion in browser extensions (c'mon it is now 2022!)

This is the NUMBER ONE REASON why I do not recommend 1password for business. I suspect the 1password test group is only comprised of consumers who test it on sites like amazon.com or citi.com. If you work at any type of business that has in-house web-based applications, subdomains are VERY widely used. Every time I need to log into one of my own sites I have to scroll through an endless list of logins in 1password. It's really annoying. If I had known about this limitation when evaluating password management for my organization I would have picked a different company, no question. PLEASE add this or at least acknowledge it's coming soon. Getting ready to roll this out to 2 more departments.

PLEASE, as a developer with prod vs test done by subdomain (and literally hundreds of test accounts) this is crucial to be able to actually find the right login.

+1 vote

Very very long awaited feature.

+1 vote as well

Yeah unfortunately pretty ridiculous.

It is hard to believe that such an important and hundreds of times requested feature (there is more than one thread about this feature) is neglected for so long. Since some competitors' products offer this feature, there should be no general technical reason not to implement it. For some inexplicable reason they just don't want to implement this feature...

Yeah unfortunately no one cares about it from 1Password.

+1
This is really something so basic that shouldn't even require much noise
The subdomain specific entries should be at the very top in suggestions

+1

Please add my vote as well.

In the end we have to conclude that the browser extension is unusable if you got hundreds of logins under the same root domain with different subdomains.
The autofill doesn't help at all and we stopped using it since out of a list of >100 entries it is impossible to pick the right one.

An absolute deal breaker for 1Password in general.

And I'm sorry this major usage bug is open since 2017. This is absolute nuts. For one of the most expensive password managers out there this is really crazy and embarrassing. (considering the funding you get)

And just for your info the explanation from 2017 is well known (https://1password.community/discussion/comment/348474#Comment_348474) but this can't still be the reason for driving 1password unusable. Just store the login items hashes of the root AND subdomain (a.b.de -> HASH, b.de -> HASH) and it would be no problem to suggest the correct login items in the correct and usable order. (since the browser extension can generate hashes for the current domain on the fly)

Implementation suggestion:

Map not encrypted:

HASH for a.de -> Login Item A
HASH for b.a.de -> Login Item A

Browser extension:

Current website (b.a.de)

-> Generate hash for "a.de" and generate hash for "b.a.de" and look into the unencrypted map.

Et voila you can suggest both items without even a single need of decrypting it beforehand. It is as simpel as that.

This is not some kind of micro bug this is a major flaw since it drives the browsers autofill unusable. And guess what employees started to activate Chromes password manager to save the passwords due to this major usability flaw. (since the autofill of chrome just works perfectly...)

And this makes it a major security bug!

I'm really angry that this one gets ignored now for more than half a decade.

Just embarrassing.

PS: For private use this is not a problem since you normally don't have multiple login items for the same domain. But for business usage especially in the field of web development agencies it is an absolute mess. All the login items are cleanly separated by subdomain but get all suggested at once.