1835410 - Missing support for caBLE in WebAuthn

Status: NEW

(Web Compatibility :: Knowledge Base, defect)

Description

[Ksenia Berezina [:ksenia]]

Symptoms:

• Users are unable to use Google's "Built-in security key" on Android to sign into an account

Additional notes:

• Even though this is affecting Google's sign in process, the issue is only
  affecting users who want to add their Android phone as a security hardware
  token, and the assumption is that this is a relatively small subset of users.

Comment 1

[Stefan Fleiter (:sfleiter)]

(In reply to Ksenia Berezina [:ksenia] from comment #0)

• Even though this is affecting Google's sign in process, the issue is only
  affecting users who want to add their Android phone as a security hardware
  token, and the assumption is that this is a relatively small subset of users.

How do you come to that conclusion Ksenia?
I doubt many users want to buy a FIDO2 device and carry that around.
If Passkeys are supposed to reach the masses the solution needs to be easier and cheaper than that.

I still hope passkeys can help to get rid of the several 2FA solutions I need to use from company, bank accounts, etc...

Comment 2

[Dennis Schubert [:denschub]]

How do you come to that conclusion

Because we can track the report volume about this over time, and it's lower than some of the other WebCompat issues we experience and work on, and thus it's less important.

If Passkeys are supposed to reach the masses

This isn't about Passkeys, it's about caBLE specifically. Bug 1838015 is about passkeys.

Comment 3

[Amit Prakash Ambasta]

I don't think that's a fair assesment. In my company alone, around 20k folks are using passkeys via CaBLE, but on Windows/Chrome (Gsuite Advanced Security)

However, I've come across a handful of people who actually carry a FIDO2 device