Password selection filter is not specific enough for sub-domains
When logging in to one host on our domain I currently have to wade through all passwords for our domain searching for the right credentials.
Our domain is co.apache.az.us which makes hosts something like www.co.apache.az.us. I have noticed that 1Password does not match to the hostname level, only a predefined number of subdomains. Is it possible to get that level extended or added as a configurable item?
1Password Version: 7.3.684
Extension Version: 4.7.4.90
OS Version: Windows
Sync Type: 1Password Enterprise
Comments
-
Hey @headhertz! Could you clarify for me what behavior you're seeing exactly? In other words, what's a URL that you'd visit in your web browser, does that item in 1Password have that exact website value as well, and what are you seeing (or not seeing)?
If I visit https://co.apache.az.us, 1Password mini shows the exact result, no wading necessary:
It'd be awesome if you could give me a concrete example so I can better understand the scenario at hand and see what we could maybe be doing better. :smile:
0 -
Thanks for the reply, ag_mcarlyle. I set up a test environment and found a few things.
- Exact Match results ARE filtered to the hostname level. I was wrong about this.
- Exact Match results are hostname but not directory specific. https://test.com/a/ is the same as https://test.com/b/. This is where my Exact Match duplicates are coming from.
- Close Match results are specific to three-places. ie x.x.x. I had previously not noticed the Close Match distinction.
You can disregard this request.
0 -
Hey @headhertz, thanks for the additional details! You're correct that we currently ignore anything after the
.com/for matching purposes. I can see how this could be useful in this instance, but in general I think it could get a bit messy. Imagine someone who visits https://www.amazon.com/sign-in and is frustrated when their Login that has https://www.amazon.com/profile as its saved website doesn't show up. 🙂0
