Missing support for CTAP2/FIDO2 in WebAuthn
Categories
(Web Compatibility :: Knowledge Base, defect)
Tracking
(Not tracked)
People
(Reporter: ksenia, Unassigned)
References
Details
User Story
url:login.live.com/* url:mysignins.microsoft.com/* url:login.yahoo.com/*
Symptoms:
- Users are unable to add a hardware security token to an account
- Users are unable to use Windows Hello to sign into an account
Additional notes:
- Even though this is affecting big properties, the issue is only affecting
users who want to set up 2fa with a hardware token, and the assumption is that
this is a relatively small subset of users.
Reporter | ||
Updated•2 years ago
|
Reporter | ||
Updated•2 years ago
|
Comment 1•2 years ago
|
||
This affects users in our enterprise (including me) as we will be forcing phishing resistant logins in Entra, any plans to address this asap?
Comment 2•2 years ago
|
||
People are actively working on it. There are still a few remaining tasks, which you can discover by following the bug that is linked in the "depends on" section of this bug. All Bugzilla bugs have a "follow" button, and if you click that, you'll get updates per email as they happen. If you find a specific bug in our already-shipped implementation, please file a bug. But otherwise, please don't post "are there updates?" questions here - this is our workplace, and we try to keep the information density in bugs high.
Comment 3•1 year ago
|
||
In general, we support CTAP2 now. There are some remaining issues with Microsoft domains, but these are due to user agent sniffing and not lack of support.
Description
•