Open vwbusguy opened 5 years ago
Please enable ADB, connect the device to your desktop machine and check the browser console via FF desktop's developer tools. Then please share the console logs with us. I'm sure there is one or another error logged.
overwrite.cli.url": "https:///nextcloud"
is this your actual value? This is not a valid URL. With this value, u2f won't work.
@ChristophWurst - I put REDACTED in >/< and github filtered it out. It's a self-hosted nextcloud instance.
I'll report back once I can get setup with adb and figure out how to connect desktop Firefox to it. It's odd that other websites, like Github work with Firefox on my phone. It's not even opening the Android U2F dialog.
I'll report back once I can get setup with adb and figure out how to connect desktop Firefox to it.
It's relatively easy: https://developer.mozilla.org/en-US/docs/Tools/Remote_Debugging/Debugging_Firefox_for_Android_with_WebIDE_clone
Ah … do you use a subfolder for Nextcloud?
Yes, I do.
Here's what I see in the console debugging. It looks like it's failing to load a script.
The u2f listed there appears to just be some JSON: {"message":"Current user is not logged in"}
You get an error 1: https://developers.yubico.com/U2F/Libraries/Client_error_codes.html
I do not yet know when these pop up and how to fix. It also showed at https://github.com/nextcloud/twofactor_u2f/issues/555.
Thanks the debug info!
The u2f listed there appears to just be some JSON:
{"message":"Current user is not logged in"}
Where exactly is that json from?
You can see the first line of the console in my screenshot references "u2f" which appears to be some kind of json response. I don't know more than that.
It's also weird that it's so specific. Desktop Firefox works fine. Chrome on Android works fine. Firefox on Android is where it is broken. It also seems specific to Nextcloud, since the same key/browser/device works for GitHub logins. It never actually opens the dialog where I present my key, but immediately fails instead.
Hi,
I do not have the time to dig into this any deeper at the moment. If you do, please let me know if three are any insights. Could you get it running in the meantime?
I'm not sure I have anything more to offer about it other than the same behavior persists on Fedora 31, with NextCloud 17.0.1, with Firefox (Android) 68.2.1.
Just chiming in that I'm also experiencing this issue, as described. I've updated to version 5.0.0.
Firefox does not support U2F, only its standardized successor Webauthn/FIDO2. Chrome supports both of these APIs which is why it's working, and GitHub has upgraded to FIDO2 which is why GitHub works.
This issue is a duplicate of #342.
Closing since this is a duplicate. @ChristophWurst hope I'm not stepping on your toes since I have write access from a different team :-)
Firefox does not support U2F
Actually FF works fine. I'm using it for u2f. And to my knowledge fido2 is backwards-compatible with u2f.
@ChristophWurst is right. The same browser works with my u2f mfa for my github account.
Ack, I lost track of this ticket. Turns out that U2F is enabled on desktop Firefox for compatibility reasons but not on mobile Firefox, which is why this works on the desktop but not on mobile.
You're right that FIDO2 is backwards-compatible with U2F in some cases, but I'm pretty sure that's limited to security keys. If a website uses FIDO2, a U2F security key will work with it. But FIDO2/Webauthn still uses different JS APIs. (At least AFAIK, obviously I've been wrong once already... but I'm pretty sure.)
Yeah, and this app focuses on security keys exclusively right now. There is https://github.com/michib/nextcloud_twofactor_webauthn for webauthn if you want to try that.
To be clear, I'm not using the key for passworldless authentication (which is what I assume webauthn would pertain to) but as a second factor after password.
To be clear, I'm not using the key for passworldless authentication (which is what I assume webauthn would pertain to) but as a second factor after password.
This assumption is incorrect. Webauthn is the new browser API for interfacing with the user's FIDO tokens, and as well as offering passwordless authentication it is the direct successor to U2F, offering the same second factor authentication (even with the same FIDO1 hardware) but with more consistency across browsers.
Per essere chiari, non sto usando la chiave per l'autenticazione passworldless (che è ciò che presumo riguarderebbe Webauthn) ma come secondo fattore dopo la password.
To be clear, I'm not using the key for passworldless authentication (which is what I assume webauthn would pertain to) but as a second factor after password.
Prove to install Google authenticator and testo if work on u2f to FF.
https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2
Yes, I have Google Authenticator installed (which is actually for TOTP). Like I said in my original post, this works in Firefox for other sites on the same device. I can use my key with github in Firefox on Android. I can use my key with nextcloud on Chrome with the same device. It's specific to Nextcloud with Firefox on Android.
Steps to reproduce
Note that this same Firefox browser/key/phone works with GitHub. I'm able to get the dialog and NFC auth via Chrome Browser, but not Firefox, specifically on NextCloud 17.
Expected behaviour
User logs in, selects U2F device, prompt opens to select USB/NFC, key is presented, user is authenticated.
Actual behaviour
User logs in, selects U2F device, no dialog is presented and the key check immediately fails. User must cancel login or present backup code to proceed.
Server configuration
Operating system: Fedora 30
Web server: Apache/2.4.41
Database: Mariadb 10.3.17
PHP version: 7.3.9
Version: (see admin page) 17.0.0
Updated from an older version or fresh install: Updated from latest 16.x
List of activated apps:
The content of config/config.php:
{ "trusted_domains": [