I have a main corporate account to access multiple sites/applications. For most sites & applications I have no issues, but there are a few where the username is case sensitive, so if I set it up in Bitwarden with upper cases, it won’t work for the one requiring lower cases when using autofill. If I do use autofill I have to remember to manually change the username field before clicking on login.
Is there a way in Bitwarden to set exceptions for logins to specify certain sites to use a different login name? I know I could setup a 2nd item, but then that would mean I would have to remember to change both every few months when I am asked to change the password.
I assume that you have a situation in which there are multiple sites/apps that have case-sensitive username fields, requiring different capitalizations (if only one capitalization form is case-sensitive, then you could obviously just use that capitalization across the board).
You might be able to solve your problem using custom fields. This will work if and only if the login forms with conflicting capitalization requirements have been coded using distinct identifiers for their username input fields.
As a start, go to each login form, right-click in the username input field, and select Bitwarden > Copy custom field name from the pop-up context menu. Paste the clipboard contents into a text editor, and compare the field identifiers to each other. If they are different from each other, then you can define multiple custom fields within the same vault login item, and give each custom field a name that corresponds (exactly) to the field identifier; the value stored in each field should be the username with the capitalization pattern as required by the corresponding website/app.
If you get an error message (“No unique identifier found") when using the context menu option, or if nothing is copied to the clipboard, then you would need to find the input field identifier using a manual method (described here).
Also, if you only have two username forms (e.g. MYUSERNAME and username), then you should be able to accomplish this with a single custom field (using the “csv=” prefix). However, all of this hinges on the ability to find unique username field identifiers for each website login form. Once you’ve attempted to do this and given us an update on your progress, we can provide further help, if needed.
I suspect this will be the best path forward, although you are absolutely right that “remember to change both” is the annoying bit. There is a Feature Request that would solve this annoyance. After you have browsed the community for a while (~30 minutes), you will get a notice that you have 20 votes. Afterwards, go vote for the FR.