-
Notifications
You must be signed in to change notification settings - Fork 15
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
Unable to register yubi keys #31
Comments
There is a logging option in the plug-in's settings page. Could you pls provide logs for the failed registration? |
Here is the log entry [2022-03-18 11:56:49][cc880a] PHP Version => 7.4.28, WordPress Version => 5.9.2, WP-WebAuthn Version => 1.2.6 |
The browser provides a message that I may require a newer or different type of key |
Seems like you have user verification enabled. U2F doesn't support user verification however and the procedure failed on the browser side. |
Changing that makes no difference. Seems that sodium is required. Never heard of that. [2022-03-18 19:36:53][423770] ajax_create: Start |
sodium is a built-in PHP extension for encryption since PHP 7.2. Please check your we'll add a warning in the settings page if sodium is not installed since next version. |
I have same problem. PHP 8.0, Yubikey What is sodium? :) This one? https://www.php.net/manual/en/sodium.installation.php that seems embedded in PHP? [2022-03-23 18:02:44][3375b5] ajax_create_response: Credential ID unique check passed |
It's a built-in PHP extension but not enabled by default on some PHP instance. You need to check whether you have enabled it.
Have never seen this error before. I'll try to figure it out. Sorry for the late response. |
what model of yubikey do you have, also are either |
I have ensured gmp and mbstring are enabled on my wordpress hosting site but cannot register yubi keys (including yubi 4)
Is there a restriction on which version of key can be used? The general information suggests that webauthn should work with any of the u2f keys
The only config item with mbstring that may be an issue that I can see is HTTP input encoding translation is Disabled
Does that need to be changed?
Client is gentoo linux, browser google chrome 99.0 4844.51
Thanks
Chris
The text was updated successfully, but these errors were encountered: