Advanced URL matching?

Zerosan

Pattern based matching would certainly cover most people's needs.
Supporting simple wildcards would be pretty neat.

https://\*.domain.tld:\*/\*
https://subomdain-project????.domaind.td/\*
https://domain.tld/specificpath/

Sorting the results/matches in a smart way would probably be beneficial as well,
based on most specific match: subdomain, domain, tld, port, path
I would argue sorting based on multiple of those attributes alone would already remedy this issue/requirement for plenty of people.

Khils

Hi,

Apologies if this has already been answered but I've tried Googling and am still having issues with URL matching.

I have several services running on my Synology NAS, for example here are two:

http://192.168.1.198:180
http://192.168.1.198:8989

Each service has their own set of credentials, how do I make it so that 1Password only autofills the relevant service for their URL? Currently it seems to be offering all entries that begin with "http://192.168.1.198", even if I select "Only fill on this exact domain" for each URL.

On Bitwarden it was extremely easy, I simply used the "Host" method of matching: https://bitwarden.com/help/uri-match-detection/#host

Does anyone know how to apply this behaviour in 1Password please? I'm very new to this so I'm probably missing something obvious (and I'm sure I'm not the only 1Password user that self-hosts some services).

Thanks

Zerosan

Hey Khils, what you desire is currently not possible with 1password, as it ignores the port when it comes to "Only fill on this exact domain"

Users have been asking for better matching options for years, and things have improved, but sadly very much still fall short of many other password managers.

macson

I switched to 1Password some time ago but I'm really keen on this feature. 1Password, please listen to all of us who need this feature.

tomstock

This is a much needed feature, I am getting very frustrated with 1password attempting to auto-fill my employers passwords/settings with my information

Dave_1P

Hello folks,

Thank you for all of the feedback! For those who missed the post earlier, you can adjust autofill behaviors in order to control where 1Password suggests a login. Our guide for the feature is here: Change where a login is suggested and filled

You can follow these steps to have 1Password suggest a login only on a certain hostname and port:

1. Open and unlock 1Password.
2. Locate your Login item and click "Edit".
3. Click the "Autofill behaviour" button beside the URL and select "Only fill on this exact domain".
4. Click "Save" and repeat the steps for the rest of your Login items if they contain different hostnames or the same hostnames but different ports.

If this doesn't fit your needs, and you haven't already shared your feedback earlier in the thread, then please let me know. 🙂

-Dave

dserodio

Thanks Dave, that's awesome!
Is there some way to make this adjustment using 1Password in the Browser (the browser extension)? I'm still on 1Password 7 because its UX is better than 1Password 8, but it doesn't have this feature.

Dave_1P

@dserodio

The feature to change autofill behaviour isn't available in the browser extension but, if you don't have 1Password 8 installed, you can also use the new beta version of 1Password.com (which recently gained the ability to edit and save items) to change an item's autofill behaviours: Experiment #4 – New interface in 1Password.com’s vault view — 1Password Community

1Password 7 is no longer supported and I recommend that you upgrade to 1Password 8 as soon as possible. If you do have feedback about the user experience then I'd love to hear it, you can start a new thread using this link. 🙂

-Dave

lumarel

Hi there!

Just giving my +1 here as well.
We could really benefit if we could do pattern matching for some domains, if you have hundreds to thousands of the same device type with a common naming scheme, but mixed in the same domain as many other devices (like prxxxx.example.com).
Being able to only do exact domain matching already helps quite a bit to get the detection what should stay on top of the list, but yeah that doesn't really work if all the FQDNs are different.

Cheers, lumarel

EvonG1P

Thanks for reaching out, @lumarel.

May I confirm if you are referring to Regex pattern matching? Several pattern-matching requests were previously discussed, and I want to confirm that I recorded your request correctly with our product team.

Any additional information you can share would be helpful. I look forward to your reply. 🙂

-Evon

lumarel

Hi @EvonG1P !

Thank you for following up.
Yes Regex pattern matching would definitely do the trick,
but if the team wants to stick to a simpler pattern matching like only * (pr*.example.com, aka. any character 1 or more times) and ? (pr???.example.com, aka. any character 1 time) it's also fine.

To this specific feature, there isn't much more to say than what I already did. There were other ideas back in the 7 days, but these are out of scope here :)

Thank's for listening!

EvonG1P

@lumarel,

You're welcome, thank you for the additional details. I've shared your feedback with our product team. 🙂

-Evon

ref:44248402