Teach-in credentials with browser extension

[grb]

@krizzo

Any difference to other methods, in this relation?

Not really, but I wanted to know what you did in case it became necessary for me to attempt to reproduce the issues you were experiencing.

@krizzo

BTW “Ask to add login” did not work several times, which I attribute to the assumption that the browser extension was locked from the short timeout of a minute. Agree?

Not necessarily. If the extension is locked, then you should still be prompted to save the login, with the prompt asking you to “Unlock to save this login”.

It is a known limitation that those “Ask” prompts cannot work with 100% reliability, because this functionality requires Bitwarden to inject code into the webpage HTML, and this approach requires many assumptions to be made about the website’s HTML code structure, which are not always going to be valid.

@krizzo

But I keep “Ask to update existing login” for longer because it should not harm and could be useful.

If you encounter a web page for which the “Ask” prompt does not function as intended (e.g., the prompt does not appear), then you can “lose” a password (i.e., the password is changed on the website, but not in your vault item). This (small, but real) risk is the reason why making changes directly in the browser extension is recommended by power-users.

@krizzo

It would be helpful to set the lock timeout differently on mobile devices from stationary PC. Is that possible?

Yes, every Bitwarden app or browser extension has its own timeout settings.

@krizzo

This minimalism seems to be a shortcoming of the login template, because most of the registration forms require an email address. It would be totally impractical (unworldly) to have to add the email field for every login item manually as a custom field. Really?

I disagree, because even though some registration forms may require both a username and an email address, the actual login forms seldom require you to enter a username, password and an email address. Thus, it is sufficient for the vault item to store the two pieces of information that will be required during the login process.

Regardless, if you feel differently, here is a Feature Request that you can support (by adding your perspective to the discussion, or by voting for the Feature Request after you have gained voting privileges on the forum):

Add "Username" and "Email" as separate entries for (vault) login items

Please add an “Email” field for new items. By default, if only the username or email field is filled in, use that for the login username. If both are filled in, provide a means to select which is to be used for login forms. Many web sites separate “Username” from “Email”. You need the username to login, but the email for password recovery for example. A quick button to copy email OR the username would be extremely convenient. I currently add a custom field or notes to each record to save …

 

@krizzo

If I would start the registration with the web form and fill the email, and re-activate “Ask to add login”, would BW then create an email field?

No, Bitwarden does not create any fields when you use the “Ask to add login” feature. It simply scans the web form for data to populate the existing Username, Password, and Website (URI) fields.