This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

ค้นหาฝ่ายสนับสนุน

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

เรียนรู้เพิ่มเติม

Webauthn support for firefox on android

  • 2 การตอบกลับ
  • 1 คนมีปัญหานี้
  • 1 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย TyDraniu

more options

Hi, I'm trying to test Webauthn using webauthn.io website, but it looks like none of Firefox version on Android supports it. I tried: - Firefox 81.1.4 - Firefox Beta 82.0.0-beta.6 - Firefox Nightly 201016 (Build #2015770059) all available from google play store

I found that this should be supported: https://blog.mozilla.org/security/2019/08/05/web-authentication-in-firefox-for-android/

What am I missing?

Hi, I'm trying to test Webauthn using webauthn.io website, but it looks like none of Firefox version on Android supports it. I tried: - Firefox 81.1.4 - Firefox Beta 82.0.0-beta.6 - Firefox Nightly 201016 (Build #2015770059) all available from google play store I found that this should be supported: https://blog.mozilla.org/security/2019/08/05/web-authentication-in-firefox-for-android/ What am I missing?

การตอบกลับทั้งหมด (2)

more options

Right, I found that there are settings in about:config and: - Firefox -> can't load about:config, something about bad certificate is in url after typing about:config into address bar :( - Firefox Beta -> the settings was on false, I've changes all of them to True - Firefox Nightly -> the settings was on false, I've changes all of them to True

Now webauthn.io reports that webauthn is supported but the demo doesn't work. Nothing happens after clicking register. I've also checked webauthn.me, it also doesn't work. I haven' debuged it yet with remote debugger so I'm not sure if there is any error in logs that would explain the situation.

Investigating further...

more options

It's not ready yet, please follow issue #1340 for updates.