-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FIDO U2F Security Keys not being enabled #511
Comments
hello, Yubikey work on Firefox for me, but not work on Edge browser. |
U2F no longer works in Chrome or browsers based on it. #423 has more info. The provider not enabling sounds like a different issue, though. |
Hi, U2F no longer works for me. In Chrome initially and in Safari later. Thanks for the work on this plugin. Edit: I want to provide more context on this. Please view this link deprecation Edit: this pull request migrates over to the new tech. pr. If you kindly message someone with write access and ask them to merge the pull request, we should have U2F back and running again. |
WP 6.2 |
https://wordpress.org/plugins/two-factor-provider-webauthn/ is an option in the mean time, until this plugin finishes building WebAuthn support. |
Same problem here, U2F is without function. Can neither login nor register a new key. |
FIDO not working here either |
This is a duplicate of #423, mostly. The Enabled checkbox is being saved as enabled, but the UI is not showing it as enabled as it has no keys enabled (ie. The provider isn't "available" for the user). You'll see a similar behaviour if you setup Email+TOTP+FIDO+Backup codes - if you haven't configured TOTP or Generated backup codes the Checkbox will revert to unchecked. The keys can't be enabled because FIDO / U2F is no more, and it needs to migrate (Which is what #423 is). Ideally, until #423 is resolved the U2F provider should self-disable itself (Unless there's keys registered I guess). |
two-factor-provider-webauthn gives the "serious error with this web site" message instead of "insert and touch your security key" on current WordPress, current versions of both Firefox and Chrome on my Mac (Catalina, Intel). Had to SSH in and wipe it. I realize that third party plugin is not yours to debug, but it's not a useful option "until" if it does this. |
Closing this to keep all the FIDO deprecation discussion to #423. |
WP Version - Version 6.1.1.
Plugin Version - 0.7.3
PHP Version - 8.0
Browser - Brave version - Version 1.47.186 Chromium: 109.0.5414.119 (Official Build) (x86_64)
STEPS
Enabled and setup "Time Based One-Time Password (TOTP)"
Tested to see if it works : It Works.
Checked the Enabled Checkbox for FIDO U2F Security Keys and updated profile
It reloaded with " FIDO U2F Security Keys" unchecked.
Disabled "Time Based One-Time Password (TOTP)" and updated profile.
Checked the Enabled Checkbox for FIDO U2F Security Keys and updated profile
It reloaded with " FIDO U2F Security Keys" unchecked.
Unable to enable " FIDO U2F Security Keys"
When I tried this on another cloned install of the above, I first tried FIDO that didn't work, then I tried TOTP, that didn't get enabled either, nothing was getting enabled.
I tried it on Mozilla Firefox (109.0 (64-bit)) and I was able to get it to work, I was using the Brave Browser when I was facing the above issues, it doesn't work on the Brave Browser.
Also when I try logging in on the Brave browser and use FIDO it doesn't work, it works on Mozilla Firefox (109.0 (64-bit))
The text was updated successfully, but these errors were encountered: