1748850 - Security Key Option Sign Option Not Presented on Firefox for Mac

Status: RESOLVED FIXED

(Core :: DOM: Web Authentication, defect, P3)

Description

[aamir]

Attachment: Screen Shot 2022-01-06 at 9.55.51 AM.png

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.110 Safari/537.36

Steps to reproduce:

When to Office.com to sign into my account.
Clicked on Sign in options , only option presented was sign in with github. No other option was presented.

Even changed the following settings, but no help
security.webauth.u2f true
security.webauth.webauthn true
security.webauth.webauthn_enable_softtoken true
security.webauth.webauthn_enable_usbtoken true

Actual results:

Security Key or Window Hello Key Sign in option not presented under sign in options

Expected results:

Security Key and Windows Hello Key Sign in option must be available and enabled on the browser

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::DOM: Web Authentication' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:dveditz, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 3

[Daniel Veditz [:dveditz]]

The site doesn't give the security key option for Safari, either -- it appears to be a choice made by the page. Spoofing the userAgent is not enough to get the content given to Chrome and Edge so we'll have to ask them what they're looking for. Most likely, though, they are waiting for us to support CTAP2 devices on Mac, as we do on Windows through the "Windows Hello" authentication API.

Comment 4

[Christoph Kerschbaumer [:ckerschb]]

This is more of a duplicate of Bug 1530370 - marking as P3 and we can follow up once Bug 1530370 has landed.

Comment 5

[John Schanck [:jschanck]]

The option to log in is presented in Firefox 112. There's still an issue with asserting credentials which we're tracking in 1820016.