After pressing "use security key with USB" do you hear a tone? If you wait to tap after or near the end of the tone it won't ever authenticate. Get your OTG adapter again and attempt to login again via USB. Please help me out with a brief experiment. How quickly or slowly you press the Yubikey after pressing the USB option in Google services. While you were doing that helpful experimentation I've determined it also comes down to timing. Definitely something going on with the USB implementation. I´d say, having to click a few more buttons once in a blue moon is less hassle. On the other hand, if you now go back to OTP, you not only spent time on migrating and migrating back for nothing, you also regularly have to see if it might work during the next few month only to then go through the process again and see if it really works. But maybe they just fixed the problem and you´re just fine without actually doing anything. What I´m saying is, if you only have to go through this once or twice a year, why not just leave it on for now? Maybe next time, in a few months, you go through trying it a few times again. So since you started using bitwarden, how often did you actually use the key on your phone? And don´t count those days where you just experiment with different scenarios. HOWEVER, is it really that bad? I mean, you yourself point out that on mobile, you rarely even use the key because you don´t fully log out of bitwarden. So yeah, it certainly is still a but buggy. I also, since this was necessary for NFC to work, disabled OTP for USB, but that didn´t change anything for me. With NFC, there isn´t even a google services request, it just works. So I strongly suspect it has something to do with how the USB port handles this, not how FIDO2 is implemented in general. I even had to do this five times for it to work. That google message pops up, i accept, then with two more steps I get to the actual touching of the key, which just takes me back to the start. And lo and behold, same problem as you describe.
To get a second data point though, I pulled out my Samsung OTG adaptor to try the USB process. No double or triple attempts, it just works. Since I now don´t use this feature any more, I deactivated it and that actually fixed the issue. On the BW FAQ though, they mention this and recommend to deactivate the OTP feature for NFC in the Yubikey config. Yes, at first there was a problem, namely that once I tapped the key, it always opened a yubico demo website instead of doing the actual authentication. I recently switched to FIDO2 from using OTP with my Yubikey 5 NFC. In the meantime, just tapping YubiKey immediately after selecting "Use security key with USB" works for me. Bitwarden Community thread here and GitHub thread here.
#Bitwarden android android
WebAuthn works as expected in Chrome browser on Android and in Windows.Įdit: It's been confirmed a bug by multiple people. I'm able to login using WebAuthn but it's super clunky. It's like this on my Google Pixel and another Samsung phone I have.
But it rarely if ever logs in with just steps 1-5. Bitwarden goes back to step #2 and does nothing.
Prompt comes up asking to "Allow Google Play Services to access Yubikey OTP+FIDO+CCID?" Tap OK.Tap "Use security key with USB." (I'm using Yubikey 5c via USB C).Tap the blue "Authenticate WebAuthn" button.The login flow is quite long, but would be considerably better if it didn't hang the first authentication attempt. Logging in via WebAuthn in Chrome on Android works fine.)ĭoes anyone else have to authenticate with their Yubikey via WebAuthn (at least) twice to get BitWarden to login on Android? (I should clarify this is my experience using the Android app and functionality added with the latest update.
0 kommentar(er)
