Mohamed Endisha

@conmark This is how the login flow is designed to work.

• The login form is always displayed on the login page.
• Users who have enabled passkeys can log in using the “Login with Passkey” button, which does not require a username and password.
• The username/password fields remain visible because the system must still support standard login, and when passkey-enabled users can log in via the passkey option instead.

I’ve received similar requests to disable the username/password login and show only the passkey option. We will evaluate this behavior and, if applicable, consider adding it as an option in future releases.

Thank you for your feedback and for using the plugin.

@martinfors

Thank you for your review and support; I really appreciate it. Feedback like yours helps me make the plugin more powerful and reduce errors.

It would be even better if you could share this in the support forum for wider visibility.

I will carefully check your points and try to reproduce the issue to ensure we catch them and provide a solid solution in the next releases.

—–

You can try this snippet — it will detect your subdomain rather than just the main domain:

add_filter('secure_passkeys_web_authn_relying_party_id', function ($domain) {
    $allowed_domains = [
        'sub1.domain.com',
        'sub2.domain.com',
    ];

    $host = $_SERVER['HTTP_HOST'] ?? '';

    if (in_array($host, $allowed_domains, true)) {
        return $host;
    }

    return $domain;
});

Thank you

Hello @westerdaled

As I mentioned above, Secure Passkey shouldn’t conflict with other plugins, though it’s still possible. So, has the issue been fixed, or are you looking for an alternative solution?

I also have a 2FA plugin that works well, but it only supports the default WordPress login form, not WooCommerce or other plugins.

You can check it out here: https://wordpress.org/plugins/secure-tfa

@westerdaled Thanks a lot for the feedback.

@amanandhishoe

Release 1.2.2 has been published and is now available. This update includes a fix for this issue.

Secure Passkeys here to make things easy for you.

Thanks 🙂

@girkers

The issue is not with the Passkeys plugin — it works fine.

The reason the button doesn’t do anything on your custom Elementor popup is that the popup content is only added to the page when the popup opens.

The plugin attaches its internal click listener to the button on page load (DOMContentLoaded). Since the button doesn’t exist yet inside the popup, the listener is never attached, so clicking the button does nothing.

You need to trigger the plugin initialization after the popup content is rendered. For Elementor, you can add the following JavaScript to the page (for example, in an HTML widget at the bottom of the page).

Replace id with your popup ID, in your case, it’s 423.

<script>
  jQuery(document).ready(function($) {
    jQuery(document).on("elementor/popup/show", function (event, id) {
      if (id === 423) {
        setTimeout(() => {
          const domEvent = new Event("DOMContentLoaded", { bubbles: true, cancelable: true });
          document.dispatchEvent(domEvent);
        }, 100);
      }
    });
});
</script>

I’ve tested it in your website console, and it works as expected. You can try it yourself as I did.
See the result here: https://ibb.co/pBtGH16x

I hope it works well for you, and I look forward to your positive feedback.

@bandy1967 Release 1.2.1 is now published and available. This update includes a fix for the issue.

If you find the plugin helpful, we’d greatly appreciate it if you could leave a positive review.