Exact URL matching + Port number matching filters for credential list

Please add this, it's a common feature amongst password managers, and absolutely necessary in my opinion. Being presented with 40+ options for a credential because only the main URL is considered is not useful at all!

It also doesn't remember which account was used last against a domain, I would expect the last used to jump to the top of the list.

We are currently testing a business plan for what will be 20+ users, but some of the core features are lacking against cheaper alternatives.

Yep, I totally agree with this. Although this is not a problem for me anymore, it was a huge issue when I used to work for Amazon Web Services. When working for AWS, I used to be presented with all of my personal passwords for my Amazon consumer accounts, then all of the passwords for Amazon Subdomains for internal intranet sites. But the security was so strict that there were many custom URLs that drove me crazy! (Oh, and then they insisted we all use KeePass! Arghhh!) Thankfully I don't have this problem anymore, but this should definitely be a consideration for people who use 1Password at work.

Another use case: Zoom recordings that are protected with a password. Their URLs are like https://mycompany.zoom.us/blahblah123xyz , so the domain stays the same but the rest of the URL changes.
I'm surprised that 1Password doesn't deal with this...

I came here for this exact request!

Hi, just came here to add my vote and explain a slightly different use case (or maybe this is a bug): I manage a domain with multiple environments, each with different subdomains. For the most part, my environment-specific logins (with their environment-specific subdomains) float to the top of the suggestions for those subdomains and that works great. However, the main production environment has no subdomain, and the suggestions for that page include all of the other subdomains at the top of the list, and the no-subdomain options are at the bottom. :( (EDIT: Actually it looks like they're all just in alphabetical order by subdomain or domain, whichever the URL starts with. So my "demo.p..." passwords are first, then "dev.p...", then "p..." (no subdomain), then "test.p..." etc.)

It seems to me that if the current site has no subdomain, and you have matching logins in 1Password that also have no subdomain, those should be at the top of the suggestions.

Thanks for considering!

How does 1Password decide what order items are shown as I'm not seeing the behaviour @ag_ana and @ag_chantelle are implying in 1PW8 for Mac.

For a lot of my logins, the correct option is typically the 3rd or 4th item in the list. Usually somewhere after my dev and test logins.

I'd so much prefer an option to use hostname instead of root domain for matches.

At the very least, matched subdomain items should appear before any matching root domain items. Whether they are favourites or not.

The problem is that I have favourites set for various dev and test system credentials and they're appearing before the relevant prod credentials (also set as favourites) I'm trying to login with because they all have the same root domain but not the same subdomain.

Why are favourites not sorted in subdomain order?

The extension icon list is correct.

The inline menu on the fields is not.

Just an update to say it's not just Safari I'm seeing the issue in. I'm noticing the problem in Firefox (Mac) and Chrome (Windows) although in those browsers, the inline menu seems to be "more correct" than the toolbar button.

I've been a LastPass user for quite some time, and I would much prefer to use 1password for a number of reasons. However, the inability to match passwords based on a full domain name is something which makes it an impossibility for my company.

We have plenty of internal applications which we put on a subdomain of our company domain, e.g. app1.company.com, app2.company.com. Sometimes even port numbers come into this, e.g. app1.company.com:8080, app1.company.com:8081. 1password stores passwords for these as company.com, and presents all company.com suggestions when you visit any of those apps. In LastPass, I can go to an advanced configuration option and state that company.com should use exact domain matching and/or exact port matching, which makes the problem go away - LP only shows the correct password for the subdomain.

There have been a few threads on this in the past:

• https://1password.community/discussion/87028/stricting-url-matching-for-subdomains (many "me too" replies!)
• https://1password.community/discussion/78850/strict-url-detection
• https://1password.community/discussion/119350/strict-url-matching

The responses previously were that the suggestions still showed the site they were for, which was true for the desktop app, but NOT for the android app - going to any of our sites on android would offer multiple suggestions for "company.com" without any way to discriminate which one you needed. This took it from an inconvenience (on Windows browser it's inconvenient to go to app1.company.com, then scroll down to find the app1.company.com password, but not impossible), to impossible (blindly choosing suggestions which all look the same). Worth noting that this was last checked by me when I evaluated 1p in Jan 2021 - you may have improved the android app since then.

One of the more recent threads had a "our developers are aware of similar requests" but no indication of whether this has changed status internally. I can see this answer which gives some insight into why it's tricky, but it would be nice to know whether this feature is still on a "no, we're not doing it", or has made it to a roadmap.

I raise this again because I'm part-way through a LastPass subscription, and want to know if I should be looking at 1p again when this comes up for renewal.

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided

I last looked into this issue back in January when I was after replacing my LastPass subscription. I've just created another trial to see what the current state of things is - I'll summarise my opinions below. The two cases which are important to me are Chrome and Android.

Chrome

Using browser extensions (I'm going to assume these are all roughly the same now!), what @ag_yaron has stated above fits - the suggestions are presented with the exact URL match at the top. This is workable, but still a bit inconvenient for the following reasons:

• Irrelevant suggestions are still shown, potentially causing confusion
• When saving a password, need to edit the credential name each time in order to distinguish between them in the suggestion list.

Android

When I previously evaluated this, the main problem was that the suggestion list was not ordered at all. With the current version, the experience is a bit better (I very much prefer the initiating fill from the keyboard suggestions list, this is much better than before). However, there are still 2 critical problems which make it unusable for me at this point in time:

• (Most important) - Credential suggestions are NOT sorted in the same way as in the browser, they're sorted alphabetically
• When saving a credential using the "Create a new login" from the popup suggestion list, there's no option for populating the credential name. Since the credential name is the only way to distinguish between the suggestions, this means that after adding a credential from Android, you then need to launch the 1password app, find the credential you just added, then edit the name to indicate which subdomain it's for.

All of these usability problems would disappear if there was an option for doing strict URL matching for a particular domain. The irrelevant suggestions would not be displayed, and the credential names being identical would not matter since only the relevant ones are displayed. I would not expect this to be in a prominent location of the application to avoid confusing users who won't use it - in LastPass it's buried in Account Settings, for example!

I still hope that in time this will be recognised as an important enough feature for company users and strict URL matching will arrive, and we'll be able to migrate from LastPass.

I see Bitwarden has been mentioned earlier. It does have more matching options but some do not work on Android. If you modify an entry on your desktop because you want it to exactly match a website, it will indeed work very well on desktop but that modified entry will not even show in the suggestions on Android afterwards.

There's an issue on the Bitwarden Github with a lot of valuable input that shows it's not that easy to manage that stuff on Android : https://github.com/bitwarden/mobile/issues/578