AuthLatch

Description

AuthLatch helps site owners replace routine password logins with secure passwordless access.

Key features:

• One-time magic links requested by username or email, with expiry and one-use tokens.
• Passkey login using WebAuthn/FIDO2.
• Self-service AuthLatch sidebar page for selected user roles.
• Users can add, revoke, and name their own passkeys.
• Users can send a magic login link to their own account email.
• Per-role passkey access and per-user passkey limits.
• Branded responsive login screen with method tabs for magic links, passkeys, and password fallback.
• Single active session control.
• Admin-generated login links with optional IP binding and auto logout.
• Admin-scoped login links that can block selected admin menus for that session.
• Built-in SMTP settings for hosts where PHP mail delivery is disabled.
• Audit log for important authentication events.
• RTL-friendly login UI.

AuthLatch stores magic-link validators as hashes, verifies passkeys server-side, and uses WordPress capabilities, nonces, sanitization, and escaping throughout the admin interface.

Setup

Magic links

1. Enable Magic links in AuthLatch > Settings.
2. Set the default link expiry.
3. Configure the email subject and body.
4. Configure SMTP if the host disables PHP mail.
5. Users can request a login link from the login page with either username or email.
6. Enabled self-service roles can also send a login link from AuthLatch in the admin sidebar.

Passkeys

1. Enable Passkeys in AuthLatch > Settings.
2. Select the roles allowed to use passkeys.
3. Set the maximum passkeys per user.
4. Use HTTPS on the live site.
5. Users with allowed roles can open AuthLatch in the admin sidebar and click Add passkey.
6. Users can revoke old passkeys from the same page.

Self-service sidebar page

1. Open AuthLatch > Settings.
2. Select roles under Self-Service Page > Sidebar access roles.
3. Only selected roles will see the AuthLatch sidebar page.
4. The self-service page lets users manage their own passkeys and send a magic link to their own email.

Password fallback

1. Keep Username/password login enabled if normal WordPress login should remain available.
2. Keep admin password fallback enabled if administrators should still be able to log in with a password when password login is otherwise disabled.

SMTP

1. Enable Use SMTP for WordPress emails.
2. Enter host, port, encryption, username, password, from email, and from name.
3. Save settings.
4. Send a test email from AuthLatch > Settings.

Privacy

AuthLatch stores authentication-related records in the WordPress database, including hashed magic-link tokens, passkey public-key data, hashed IP values for audit and optional IP binding, and configuration settings. AuthLatch does not store plaintext magic-link validators. SMTP passwords are encrypted with WordPress salts before storage.

Third-Party Libraries

AuthLatch includes the MIT-licensed lbuchs/WebAuthn library for WebAuthn/FIDO2 server-side verification.