Hello All,
I have been unable to read my yubikey for 2FA (FIDO2) using either NFC or USB when attempting my initial login on Bitwarden on Android (either for the app or accessing the webvault using Chrome).
The sequence I experience when attempting to login to the Bitwarden app is:
- Enter email, then master password
- An “authenticate WebAuthn” page comes up, with a toggle for “Remember” and a large button “Launch WebAuthn”
- I hit the “Launch WebAuthn” button, which then opens up a page in chrome titled “bitwarden FIDO2 WebAuthn”, a photo of a yubikey being held next to a phone, and a blue “Authenticate WebAuthn” button at the bottom.
- I hit the “Authenticate WebAuthn” button, which changes to “Return to app” but nothing else happens.
- I hit “Return to App” and receive the error “An error has occurred. We were unable to process your request. Please try again or contact us.”
- Steps 3-5 can be repeated indefinitely with no changes.
During steps 3-5 there is no response to the yubikey either at the NFC reader or USB. Initially when held next to the NFC reader it opened a yubikey test page, however following the advice of the Bitwarden “Troubleshooting YubiKey NFC” page I disabled OTP over NFC using YubiKey manager. It stopped opening the YubiKey test page when the NFC was scanned but I cannot discern any other changes. FIDO2 is still enabled for both USB and NFC.
Several posts on the forums (e.g. Fido2 Not Working On Android) reference a “toast” menu that allows you to select 2FA options - I may not be understanding what that is, but I don’t seem to be seeing it.
When I attempt to log in on Chrome, when I get to the 2FA step I immediately get an error in a pink box that appears in the top right “An error has occurred. The authentication was cancelled or took too long. Please try again.”
Thank you for your assistance. If this is outside of scope, please let me know, and if possible point me in the right direction of where to ask. There have been a couple of questions regarding this, but all of the forum posts I have found have involved solutions of uninstalling, rebooting the phone, reinstalling, etc. which I have tried in every variation I can think of.