What will this feature do differently?
At the moment only Username and Password are available in linked fields. This feature request would have a 3rd option added - OTP code.
What benefits will this feature bring?
It will allow easier login to sites which present OTP as a 3rd field on the login screen.
Remember to add a tag for each client application that will be affected
I’ve only added browser, as I suspect it would be the main benefactor. But it seems like the kind of change that would be best propagated to all platforms.
Related topics + references
Are there any related topics that may help explain the need and function of this feature?
No.
Are there any references to this feature or function on other platforms that may be helpful?
No.
It would be useful to be able to link a custom field to TOTP so that TOTP can also be autofilled, greatly reducing friction, which hopefully leads to better adoption of the feature and better security for all!
This would be super helpful for those websites that use crazy (or too generic) TOTP field names. Linked field just like they have for username and password shouldn’t be too hard to implement.
Having the ability to have Bitwarden provide TOTP is a real time-saver, when it works. It would be nice if there was the option to add custom TOTP fields for those websites that prompt for TOTP such a way that Bitwarden does not recognize it.
@quilter-anther I moved your post into the existing feature request thread. If you have any votes left to give, please scroll up to the top of the thread and click the Vote button.
The needs to link a custom field to the TOTP field is more prevalent.
Tactical RMM and other vendors that use a pop-up OTP password “attribute” field with non-standard id’s force you to manually copy the key, rather than auto-populate.
I think the feature request that you had posted in (“Allow custom field names for TOTP autofill”) was essentially asking for the same thing that you are proposing, although the implementation details were left vague (linked fields had been mentioned only in cited a comment from a since closed feature request).
Regardless, I have now merged that thread (“Allow custom field names for TOTP autofill”) with a previously existing feature request topic (“Add TOTP as a Linked Field”) which was more explicit about using the linked fields feature for allowing the TOTP field name to be recognized as an autofill target. I have also modified the topic title to be more descriptive.
The thread you referenced is requesting access to variable names (e.g., $PASSWORD) that can be used to reference the username and password fields. That is beyond the scope of the current (merged) feature request.
