I’d like to suggest a small but very useful improvement to the auto-save (auto account registration) popup.
Right now, when Bitwarden prompts to save a new login, it often saves the full URL, including long random subdomains or paths, for example: https://random123.example.com/path?...
Instead, it would be great to have an option for Bitwarden to automatically store only the main domain, e.g.: example.com
This would:
Keep the vault cleaner and easier to read
Avoid duplicate entries for the same website with different random URLs
Make logins match more reliably across different pages on the same domain
Maybe this could be a toggle like “Save only main domain” in the auto-save popup or a global setting in preferences.
Thank you for considering this feature, and thanks for the great product!
When you have saved a URL of the form https://random123.example.com/path?..., the Website address that is displayed in the View Login view is simply random123.example.com (i.e., just the FQDN — with the protocol, path, and query parameters omitted). So it is not that difficult to read.
This should not occur, if you are using the default URI matching method (“Base domain”).
Matching should occur reliably for all pages and subdomains located in the same subdomain, if (and only if) you are using the default URI matching method (“Base domain”).
What is your setting for “Default URI match detection” under Settings > Autofill > Additional Options? Are you in the habit of customizing the URI match detection method for individual URLs stored in your login items?
If your setting for “Default URI match detection” is “Base domain (recommended)”, and if the match detection method configured for individually stored URLs has been left as “Default”, then you should not be experiencing the problems that you have mentioned.
In addition, for users who want to reduce the risk that their credentials are leaked or stolen, and users who need to log in to distinct services (using different credentials) that are hosted within the same base domain, as well as users who would like to use “Autofill on page load” in a secure way, it is essential to store more than just the base domain in the URI fields (and to set the URI match detection method to something more specific than “Base domain”).