There should be an ability to add custom fields that are used universally across all sites. Recently, a change to either Bitwarden or the “master” site that I have a lot of logins for (being a developer and working with a cloud service provider) has meant that none of these sites autofill any more, and have had to go into each and every existing login to specify the custom fields. This is not a very quick process currently. I have submitted one of the sites to Bitwarden via the Google Forms a few weeks ago to have the official fields updated, but this hasn’t been resolved yet and I have no knowledge of how long this will normally take or whether it will be done at all.
As such, I believe it would be a valuable feature for users to be able to set their own universal custom fields for usernames and passwords. This would save a lot of trouble for users and give them control back around setting these up without having to repeat the process 20+ times like I did. It would be nice to have in addition to this to also prompt the user to submit the username/password fields for adding to the official list when they add a universal custom field, but not a necessity - I just mention this as I suppose the one downside to having this feature might be that fewer users submit problematic websites to Bitwarden to improve their official fields in future, and this would mitigate this downside and even make it more accessible to users.
If you hadn’t written “a lot of (different?) logins”, I would have said you can integrate many different URLs in one login item… but I think, what you target at would also be possible if this feature request got implemented:
Hi Nail, thanks for your message, but I don’t think that feature would help my use case, as all the login credentials are completely distinct. The way this site operates is that the URL will be like clientname.site.com, and so I have many independent logins stored in BitWarden using the host matching setup. These are all separate and do not share passwords and a lot of the time not usernames either.
This feature request is meant to be more around BitWarden’s autofill feature for sites where it does not correctly detect the username & password fields, and the hope was to be able to make such occurrences less painful to deal with when working using multiple logins.
So, you envision something like setting autofill rules for specific sites, that would affect all login items with corresponding URIs? (if I understood that correctly… I think there might be something in the pipeline…)
It’s probably my submission’s fault! I was forgetting there are additional custom fields in BitWarden, but I’m using the “Linked” type of custom field to specify that website page field X is the username field and website page field Y is the password field for autofill purposes, as described here: Custom Fields | Bitwarden
This allows you to tell BitWarden which fields it should fill for the username & password, but it has to be done for each login entry in BitWarden.
What I would like is the ability to add a username and password linked custom field universally for all sites, so that wherever such a field appears on any website, it is able to autofill them.
For the site I am mostly using, the input field tags have the ID “loginEdit-el” and “passwordEdit-el”, and so I would want these to always be used for autofill for username and password respectively across all of my logins. Currently it is a case of editing every login to add both linked custom fields, which is quite tedious when I have so many logins and know that these field IDs are identical across all of them.
Sounds to me like @Harvey is suggesting that instead of the list of autofill field names be hardcoded in static variables, instead they be in a user-editable list.
Yes more or less, though I would prefer that the user manageable part be something that’s in addition to the static list - i.e. an extension to them that is at a broader level than per-Bitwarden-entry (as we currently have with the “Linked” custom fields per-login). I wouldn’t mind if this was per-domain, or if we had similar options to how login matching works (i.e. host, base domain, exact), but definitely some option for creating broader user-customisable field mappings for username and password.
Probably similar to this other feature request then:
@Harvey as written before, I think Bitwarden is developing something like this. Here is a video of an early PoC… so, the release version of “Fill-Assist Targeting Rules” will probably be somewhat different… BTW, no secret knowledge – you can see on GitHub that this is being worked on at the moment…