-
Notifications
You must be signed in to change notification settings - Fork 150
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
Cannot register Yubikey with Chrome #116
Comments
U2F requires HTTPS. Do you have that? |
I've gotten the same thing on a couple of my Wordpress sites (though not all), and all of them have HTTPS. I'm running Chrome 49 on Windows 10. All the sites I'm having trouble with have been around for a while, and have/had several plugins, so I think it might be some kind of plugin conflict. Interestingly, they have all had other two-factor plugins previously as well - either Google Authenticator or Authy - so maybe it's related somehow. |
I retract my previous theory - it turns out the answer is much simpler than that (at least for my situation). I noticed closed issue #89 that was very similar, and, based on the comments there, checked out the console. That's when I noticed it:
The appId was just http, not https. Back when I converted all my sites to HTTPS, I did so with server redirects. In doing so, I forgot to go to the General Settings in WordPress and change the WordPress Address and Site Address URLs to https. I went in, changed those settings, and tried adding the U2F key again, and it worked - on all 4 sites that it wasn't working on before. WordPress in general had been working fine with just the server redirects for over a year, but that little oversight seems to be what caused U2F to fail. |
Bingo! Thanks for your research! Norbert |
One more thing: After changing the http to https, and unconditionally returning true in So it would be nice if this would be supported from the plugin out of the box. |
Thanks - any chance on the firefox extension plugin support? |
Thanks! |
Hi,
I am trying to register my yubikey neo with the plugin, but then clicking on "New" it an instant it changes to "Failed" without me doing anything.
I am running chrome 49, and verified on the yubico test site that the key can be used with this browser.
OS is Debian/unstable.
Thanks
The text was updated successfully, but these errors were encountered: