without any active doing from my side suddenly when I am prompted in Chrome in Windows10 to confirm my U2F Security Key I am also presented with the option to confirm my identity with my (android) Phone.
When I check the 2 factor authentication page in my bitwarden account I can see a second entry under WebAuthn besides my U2F key, but this one is not removable.
I do not want the option to confirm my login with my phone, I want it to be strictly with the U2F key. I haven’t found anything yet how to get rid of the phone as an authentication mechanism, I only could backtrack it that it somehow seems to be related to google chrome and/or my google account.
Help is appreciated, thank you.
I hope it’s not super belated, but I’m seeing this as well. To be safe, I’d like to remove the WebAuthn entries. However, as mentioned above I don’t have a means of manually removing these ones.
It’s a new feature from Google (Chrome). If you’ve never added your phone to your Bitwarden account Webauthn 2FA, your phone couldn’t be used as 2FA device.
I suggest everyone having this issue to go to their Google Account settings and check their GOOGLE options for MFA. Especially if they are on mobile, because I believe you gave Google Play Services permission to use your phone as a security key.
I became the owner of my first set of yubikeys yesterday and this was my first (and hopefully only) problem with them. They work as expected now.
Sorry, somehow I completely missed this. NO! You don’t want to remove that. Your phone is a security key in and of itself. Google jumped on the Yubikey train long ago (we wouldn’t even be talking about them without it honestly) and your modern Android phone is fully FIDO2 compliant.
That option will delete your access from your Google account. Not insurmountable, but it could be very inconvenient for a few days.
What I was talking about is a little dialog box when you use the Yubikey on a service for the first time.
I’ve since found that clicking “Remember this device” will cause the same behavior–you can log in with no Yubikey. You can fix this by going to any service that requires it and telling it to forget all sessions.
As usual with Bitwarden, make sure your recovery strategy is good and logout+in on all your Bitwarden clients.