Bitwarden looks for HTML input fields that it can map to username, password, or TOTP/verification code. Many sites don’t use a standard <input name="totp"> or similar identifier; they may call it something like token, otp, code, etc. If Bitwarden doesn’t recognize it, it may “misfire” and paste the wrong value (e.g., username into the TOTP field. The custom Linked field allows users to the field’s html id, name, aria-label, or placeholder. However, the only options are to specify username or password. TOTP/verification code woud be an excellent enhancement of this feature.
1 Like
@Noel_Proffitt Welcome to the forum! I moved your post into an existing feature request on the same topic.
1 Like
I want this too!
1 Like
This FR really needs to be added in the next Roadmap!
1 Like
Honestly, just being able to right-click and copy field name > new custom (linked) field > TOTP would be huge! Viola, you’re up and running. Should Bitwarden (carefully) expand the field names recognized in the autofill reader? Yes. Does this give anyone who’s using a page with unrecognized field names more power to fix their own stuff? Absolutely. And besides, there are some things in the world that don’t use anything even close to the right field name that will basically never get added no matter how much BW tries to expand the field recognition dictionary. For an IT example, routers, switches, servers, etc. admin login GUIs are/have adopted MFA, but most devices call the TOTP something proprietary or completely unrecognizable.