4 ms·

I could never get it to work on Android phones. The FIDO2 implementation of CTAP, short for Client to Authenticator Protocol. I tried registering it on many sit

I could never get it to work on Android phones. The FIDO2 implementation of CTAP, short for Client to Authenticator Protocol. I tried registering it on many sites including https://webauthn.io/ https://webauthn.io/ and it never worked. I tried it last with the Google Pixel 4 with the latest software update. Anyone get it to work Android phones? If so where?

agl 4y ago
Support is not yet available on Android but support for syncable passkeys on Android was announced for some time this year at Google I/O.
- notlukesky 4y ago
  But in every FIDO2 registration there is a pop up for both Android phones and USB security keys with the API call. The prompt for registering a device shows both "Add a new Android phone" or "USB security key". When you click on "Add a new Android phone"it leads to a barcode that when you scan nothing happens. Seems real confusing especially if they want broader adoption.
  - agl 4y ago
    2nd-factor WebAuthn should work fine with Android phones today. Any Android phone with a current version of Play Services and Chrome should be able to scan the QR code, if it doesn't work then it's a bug (or, at least, an old QR scanner). When you say "nothing happens": what's the QR scanner? Do you have Chrome installed on the device? What are the app versions (from Settings) of Play Services and Chrome?
deleted 4y ago
[deleted]
tialaramex 4y ago
I'm not sure what "it" is in this context. I have a Pixel 2 which is (consults list) registered at Google, Login.gov, DropBox and GitHub. Most other places I have only my physical Security Keys registered, but those I added the Pixel 2. In particular it isn't registered at Facebook because I only book faces inside the dedicated Firefox container on a single machine in a single location, so as to reduce my exposure. In my experience as the phone gets older features start to "deteriorate". For example, the previous phone didn't make or receive telephone calls after a few weeks without rebooting, this Pixel 2 ceases to work as a Contactless payment device after a few days without rebooting, and FIDO is the same way, so, maybe try rebooting? I figure that one day Google will rewrite their core systems in Rust or some other language that reduces the rate of heisenbugs and they'll have fewer features that "deteriorate" in this way. Also I should buy a new phone at some point.

agl 4y ago

Support is not yet available on Android but support for syncable passkeys on Android was announced for some time this year at Google I/O.

notlukesky 4y ago
But in every FIDO2 registration there is a pop up for both Android phones and USB security keys with the API call. The prompt for registering a device shows both "Add a new Android phone" or "USB security key". When you click on "Add a new Android phone"it leads to a barcode that when you scan nothing happens. Seems real confusing especially if they want broader adoption.
- agl 4y ago
  2nd-factor WebAuthn should work fine with Android phones today. Any Android phone with a current version of Play Services and Chrome should be able to scan the QR code, if it doesn't work then it's a bug (or, at least, an old QR scanner). When you say "nothing happens": what's the QR scanner? Do you have Chrome installed on the device? What are the app versions (from Settings) of Play Services and Chrome?

deleted 4y ago

[deleted]

tialaramex 4y ago

I'm not sure what "it" is in this context. I have a Pixel 2 which is (consults list) registered at Google, Login.gov, DropBox and GitHub. Most other places I have only my physical Security Keys registered, but those I added the Pixel 2. In particular it isn't registered at Facebook because I only book faces inside the dedicated Firefox container on a single machine in a single location, so as to reduce my exposure. In my experience as the phone gets older features start to "deteriorate". For example, the previous phone didn't make or receive telephone calls after a few weeks without rebooting, this Pixel 2 ceases to work as a Contactless payment device after a few days without rebooting, and FIDO is the same way, so, maybe try rebooting? I figure that one day Google will rewrite their core systems in Rust or some other language that reduces the rate of heisenbugs and they'll have fewer features that "deteriorate" in this way. Also I should buy a new phone at some point.