Domain URL matching rules
Proton pass should have URL matching rules like bitwarden. This makes it easier to handle different usecases.
For instance, at work I have different usernames/passwords on different subdomains and I would like to be able to limit certain credentials to specific subdomains and have others shared accross multiple subdomains.
So that would be great to have a diffrent matching rules like:
- root domain
- hostname
- starts with
- regex
- exact match
- ...
-
ryefly commented
Proton Pass stores URLs differently than 1P. How does Proton Pass ensure that login information is not inserted into a fake site?
-
JD Stealth commented
I find it interesting that it is assumed by Proton that a top-level domain is specific to one account/password. Subdomains and port numbers for that matter, are most definitely associated with different logins. I do not like it that Proton Pass lists ALL of my logins associated with my TLD, regardless of the fact that I have different logins associated with the subdomains. Surely, this is just an oversight, rather than a deliberate "feature"? Let's get this fixed, so that I can stop using Bitwarden. I really want Proton Pass to be clean and crisp.
-
DedoyXP commented
I'm one this feature away to switching from bitwarden (new bitwarden looks bad for me)
-
Andrew commented
This is a much needed feature. I am hesitant to full move over from LastPass at the moment because of it.
-
erictheberry commented
My needs match Farid and several other commenters. Currently juggling 20+ different sets of credentials for my self-hosted services. Please please please add this feature. I've been a Proton supporter for years, and while my continued support does not hinge on this, it would be greatly appreciated.
-
Farid commented
Pretty crucial feature. I have switched from 1Pass and I want Proton Pass to support this. I have same issue with my work related credentials where they are mostly under same domain but different subdomain for different web apps.
Proton Pass dev team, Please include this feature...
-
Ryan Harris commented
This is extremely important to me and I believe every single Password Manager no matter what should have this critical and crucial feature; it's something that if any password manager lacks makes the password manager feel a lot less efficient to use so I would definitely love for this feature to be added as I used it all the time in the past with my former Password Manager.
-
Brancu Alexandru commented
This would be extremely useful. For example I would love to separate by port.
-
Anonymous commented
I second @Todd R's comment from August 28, 2023.
Would like to have all of the items below as options:
- "full URL" to match the whole host address, port and full path
- "exact host" to avoid matching any subdomains
- "exact port" to avoid matching services on the same host which use different ports
- "exact path" to ensure matching a for login page, and not a user management page -
Shell F B Accounta commented
Subscribed to pass plus only to find out this essential feature is missing. Going to cancel my sub. I will resubscribe once this feature is added.
-
mewmew commented
This feature is essential, proton pass is useless for my home network without this.
-
David commented
This functionality should be at the core of the application. As others have pointed out, if you use this for work then it's often the case that internal domains are the same but individual systems are called with fqdn. server-a.domain.com or server-b.domain.com etc
-
Miguel Duarte commented
I’m considering to abandon my Proton Pass subscription and go back to my previous Password Manager due to the lack of this feature.
-
Grimore commented
I'll use proton pass when this feature will be available. For now, proton pass is unusable for me
-
gzw5768j commented
Just another human chiming in that Proton Pass isn't valid or usable for me without, at the very least, subdomain/host-based differentiation for logins.
-
Abufari commented
Yes that's essential to me as well
-
Ewenlau 1 commented
This is absolutely critical if you host multiple services with different authentication on multiple subdomains, like I do. I don't quite get why this isn't already implemented.
-
Tanner Richey commented
I still want get prompted to autofill the main login page, to NS1 for example, but NOT have a proton icon on every field on subsequent pages because then I am creating DNS records and never want that saved and the fill box is small enough without a icon in it I have to work around. I disabled for this site now, so my work is much less impacted but I lost my autofill on parent login page. Specifically, keep autofill on https://my.nsone.net/#/login but disable on https://my.nsone.net/#/connect/dashboard or anything else https://my.nsone.net/#/* thats not "login". So either allow exact only match, just not domain, or allow regex I can exit to exclude as my regex skills permit.
-
Des Bw commented
Adding a regex option for matching could solve it for all.
-
Steven Callister commented
This is a must have feature. Hoping this can happen ASAP.