Does Bitwarden allow me to ignore specific fields? For example, a webpage I use has some hidden fields that contain validation data and Bitwarden thinks it’s asking for a username (so when you use Ctrl+Shift+L to fill a password on that page, it overwrites the data in the field, causing issues).
I’ve reviewed the article here: Auto-fill Custom Fields | Bitwarden Help Center but this isn’t to add specific fields to fill, it’s to remove them.
I’ve also already reported the fill issue using the form here: https://forms.gle/NcZ2BmLfKH9txCzz8 but this isn’t mobile specific so I don’t know if it’s needed.
grb
June 5, 2023, 5:31pm
2
Try defining a custom text field that has a field name matching the id
attribute of the hidden input field, but that has a blank value.
If possible, please share what website you are trying to log in to, as this will assist with troubleshooting.
1 Like
Well that is an unexpected idea, but works a charm.
Anyway to do a linked field to a TOTP? I can do a separate topic if need be.
grb
June 5, 2023, 6:13pm
4
Linked fields only work for usernames and passwords, unfortunately.
Gotcha. I will submit a feature request then.
EDIT - for those looking, vote here: Add OTP as a Linked Field
grb
June 5, 2023, 6:35pm
6
In case you’re not aware, Bitwarden automatically places the generated TOTP code onto the system clipboard when you autofill the username & password fields (e.g., using Ctrl +Shift +L ).
Thus, you can just follow the Ctrl +Shift +L autofill with a Ctrl +V to paste the TOTP code.
Yep, am aware and heavily use the shortcut, the only thing is I’d like to have 3 less buttons to push (click in the field, ctrl+v, enter) if possible.
It’s not laziness, it’s efficiency .
grb
June 6, 2023, 3:13am
8
Here’s another Feature Request that you may want to vote for:
Hello, I just purchased premium. Great program, I love the convivence it brings for the level of security.
I would like there to at least be an option to autofill TOTP code while autofill option is on. This would keep users who like the current setup happy while also being useful to users who value convivence like myself.
I see this feature as extremely needed on mobile, where it takes far longer to enter TOTP code.
Please correct me if I’m wrong and there’s already a way to autofill TOTP cod…
There is even a Pull Request, although it appears to be stalled at the moment:
bitwarden:master
← andrewda:totp-autofill
opened 09:25AM - 27 Oct 21 UTC
## Type of change
- [ ] Bug fix
- [x] New feature development
- [ ] Tech debt… (refactoring, code cleanup, dependency upgrades, etc)
- [ ] Build/deploy pipeline (DevOps)
- [ ] Other
## Objective
This PR allows Bitwarden to auto-fill TOTP fields in a login form, reducing hassle from having to click on another input box and paste in the code.
Most websites that have a TOTP requirement in the sign-in process do so on another page, while some have a box on the page alongside the username and password. While this change works for both scenarios, currently you would need to auto-fill twice if there is a separate TOTP page (including sites like GitHub, AWS, Google, Cloudflare, and most other big-names). However, if the "Enable Auto-fill on Page Load" option is enabled, the TOTP will be automatically filled after being redirected to the TOTP page.
## Code changes
`src/services/autofill.service.ts`:
- Added a new array of TotpFieldNames
- Switched several synchronous methods to `async` in order to facilitate generating the TOTP code (which must be done asynchronously)
- Added a new `findTotpField` function, which uses similar logic to the existing `findUsernameField`
## Testing requirements
- Ensure TOTP autofill works on a range of websites
## Websites tested
- [x] AWS
- [x] Cloudflare
- [x] GitHub
- [x] Steam
## Before you submit
- [x] I have checked for **linting** errors (`npm run lint`) (required)
- [ ] This change requires a **documentation update** (notify the documentation team)
- [ ] This change has particular **deployment requirements** (notify the DevOps team)
It’s a great idea, although it seems to target Autofill and the previous idea targets all sorts of fill (including manual).
For security reasons, I don’t use autofill (although many of my users do)