| 开发者 | planet9 |
|---|---|
| 更新时间 | 2026年10月9日 22:48 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 or later |
| 版权网址: | 版权信息 |
[threeway_login_passkeys] shortcode on a protected page.
After each new login, users without a passkey can see the setup invitation once. They can create a passkey, close the invitation for that login, or choose not to see it again. It is not shown when the user already has a passkey or has permanently dismissed the invitation.
Settings
Open Settings → ThreeWay Login to choose the default method for browsers without a passkey and to customize the login email subject, introductory text, accent color, and passkey invitation.
Requirements
Passkeys require HTTPS and a browser with WebAuthn support. Local development on localhost is also supported.
Email codes are sent through the standard WordPress wp_mail() function. Reliable delivery depends on the website's email configuration. A properly configured transactional email or SMTP service is recommended.
No. The classic WordPress password form remains available as one of the login choices.
Yes. A signed-in user can add a passkey from the WordPress profile screen or from a protected page containing the [threeway_login_passkeys] shortcode.
No. A user first signs in with an existing method and creates a passkey. Future logins can then use that passkey.
No. Codes are sent only to email addresses already attached to a WordPress account. The response does not reveal whether an account exists.
This is intentional. Showing a different response would allow attackers to discover which email addresses have accounts. No email is sent and no login can succeed when the address is unknown.
The plugin uses the website's normal WordPress email system. Check spam filtering and configure a reliable transactional email or SMTP service if normal WordPress emails are not delivered reliably.
This initial release changes the standard WordPress login screen. The created WordPress session works normally throughout the website, but direct integration into custom login forms is not included yet.
For passkeys, WordPress stores the public credential, a signature counter, creation date, and last-used date. Private keys never reach WordPress. Email login temporarily stores a hashed code, user reference, expiration time, and attempt counter. Temporary code data expires automatically.
threeway-login slug.