-
-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improved way to match entries to URLs #137
Comments
Thank you. I'm going to close this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As mentioned in similar issues, it would be nice to have an improved, more flexible way to match credentials to URLs.
Expected Behavior
Using regex or wildcards it should be possible to match all domains where the user logs-in with the same account to a single DB entry.
Current Behavior
As of now it seems that new entries are simply associated with the current URL and then stored in the DB. This is how most browser-based password-managers work, but:
In some cases, such as Microsoft services that all have separate domains which are accessed with the same Microsoft-account, this means that my DB ends up with several entries that actually just duplicates of one another. In some cases this also leads to dozens of duplicates, for instance if I need to login to several different "country versions" (.com .co.uk ...) of the same domain, like on eBay.
This also means that changing credentials means that I need to change them for all of these duplicate entries.
Possible Solution
By using a user-provided regex in the URL field, the plugin could match multiple domains to a single DB entry. This would allow slightly advanced users to drastically reduce the clutter in their DB in such cases, while also make credential updates easier.
The text was updated successfully, but these errors were encountered: