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
- ...
celibacy040
shared this idea
-
Mathieu
commented
I won't switch to Proton Pass without this feature. Absolutely mandatory. I'm staying with Bitwarden.
-
Todd R
commented
I'm slowly coming around to the way Proton Pass does URL matching with URLs included on each password entry versus the global URL matching that LastPass does.
Regardless of whether Proton Pass continues having URLs managed in individual password entries or globally at some point, each URL entry should have a way to configure how it will match. I hope to see options for:
- "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 pageAllowing regular expressions with these options would make an incredibly powerful and flexible way for users to control when matches are offered.
-
Quentin
commented
Also waiting this feature…
I am in the same use case both, for work and for personal. -
Chris H
commented
This is massive and the primary reason I am not using ProtonPass yet.
-
Remco
commented
Create option(s) where an username/password should be used (or not be used) based on arguments like:
base domain; exact match; regular expressionand more