Axton

The UI does need improvement, and a new UI is actually on the way. It would be more clear. However we’ve decided to slow down the development to see how the current wp things go, so new features may take some time to ship.

The plugin would preform some compatibility check before allowing users to register new passkeys. Basically it checks if the required PHP extensions are installed and if the site is running under HTTPS. You should see warnings on the top of the plugin’s settings page (side menu – settings – wp-webauthn) if something is missing. The plugin needs some PHP built in extensions (gmp, mbstring, sodium) to work, but they may be missing on some PHP installations. If you are missing some PHP extensions and you’re not sure how to install them please ask your server service provider

Hope this helps

Hi richards1052,

could you please check if you have disabled user verification (which is not supported by android devices)? If you still have difficulty with passkeys on android devices, could you please enable logging in the plugin settings page and send us the logs through GitHub issue/wordpress support forum, so we can look into it? Many thanks

sorry if this plugin isn’t working for you and hope this helps 🙂

Hi levismodding,

I understand your concern. I’m working on the plugin right now 🙂 so please rest assured it is not dead.

Here’s the situation. Due to my personal circumstances I did pause the development for a while, and since this plugin is based on https://github.com/web-auth/webauthn-framework which had just released version 5.0, I’m currently working on make the plugin compatible with this new version (and also new webauthn standard). I’ll publish updates once all these work done.

as for the “compatibility” tag, I’ll update it once I get current version tested on the latest WordPress.

Hi serpentes,

Sorry it takes some time to reply but unfortunatly I cannot reproduce this error on my end. I have tested wp-webauthn on a freshly installed wordpress instance and everything works. I’ve also tested some plugins that I identified from your error log (e.g. “Content Views”) but no error is found.

It is possible that this error is caused by another plugin, could you pls try deactivating other plugins and try again? If we can locate the incompatible plugin we may be able to fix it

Hi kitchin,

1. Yes, and this plugin is not offering a new login page so users have to use wp-login.php. This plugin adds some buttons and text fields to wp-login.php so users can login using WebAuthn. Everything else is just like before.
2. This shortcode is to embed a login form that supports WebAuthn login in your pages.

Hope this helps.

Hi jeromerdlv,

Thank you for clarifying your concerns. For “better control”, I mean sub sites should have options to opt in or out the auth set up for the whole network. However sometimes this is conflict with the “website domain” option since authenticators only work under the domain they registered. We’ll try our best to carefully design and implement all these features so that the options work intuitively.

Sorry for the late reply. Hope this helps.

Hi johnmontfx,

Thank you for reporting, I can now confrim this is a bug. Will fix asap.

• This reply was modified 2 years, 7 months ago by Axton.

Hi olli23,

The logs look fine. Have you enabled PHP warning output? For back-end, WP-WebAuthn sends messages in certain format to front-end. The front-end will show errors if messages sent by back-end cannot be parsed. If your PHP is producing warnings and warning output is enabled, it will happen.