QRAuth

QRAuth replaces the password field on your WordPress login page with a drop-in QR widget. Users sign in by scanning with the QRAuth mobile app; a cryptographic signature is verified server-to-server before WordPress sets the auth cookie. Social login (Google, GitHub, Microsoft, Apple) is brokered by QRAuth’s hosted approval page, so you never have to register an OAuth app or hold a client secret.
One Client ID is the only configuration. Paste it into Settings → QRAuth and the widget appears on wp-login.php. Everything else — the approval flow, the signing, the token refresh — lives in the QRAuth platform.
Account safety is the default. Auto-provisioning is off out of the box: only WordPress users who already exist (matched on email) can sign in via QRAuth. Flip on auto-provisioning and new users are created as Subscriber — that’s the only role available, intentionally and at every layer (settings UI, sanitiser, runtime). Operators who need a different role for an individual user can change it manually via Users → All Users after their first sign-in. The plugin never stores the signing material, never issues a redirect outside your site, and never touches your user table on uninstall.
Self-hosted, no third-party scripts on wp-login.php. The QRAuth web component ships vendored inside the plugin — the only outbound call is from your server to QRAuth’s verification endpoint during a sign-in attempt.
Open source build. The compressed JavaScript at <code>assets/js/qrauth-components.js</code> is built from publicly available TypeScript source at https://github.com/qrauth-io/qrauth/tree/main/packages/web-components. The unminified source files are also vendored alongside the minified bundle inside this plugin (<code>assets/js/source/</code>) for offline review. See the Source section below for build instructions.
<h3>External services</h3>
This plugin connects to QRAuth (https://qrauth.io) — the identity verification service that performs the actual passwordless / social sign-in. QRAuth is operated by ProgressNet, the publisher of this plugin. Without QRAuth there is no widget and no sign-in.
What the service is and what it is used for
QRAuth verifies that the user who scanned the QR code (or completed a social-provider flow on the hosted approval page) is the same person who initiated the sign-in on your WordPress site, then returns a signed assertion that the plugin uses to set the WordPress auth cookie.
What data is sent and when
<ul>
<li>Auth-session creation — when a visitor opens a page that hosts the widget (wp-login.php, the registration form, a shortcode-enabled page, or a WooCommerce sign-in form), the plugin’s same-origin REST proxy sends your Client ID, Client Secret (server-side only — never exposed to the browser), and the host page URL to <code>https://qrauth.io/api/v1/auth-sessions</code>. No visitor data is included in this request.</li>
<li>Sign-in verification — when the visitor approves the sign-in (by scanning with the QRAuth mobile app or completing a social-provider flow on QRAuth’s hosted approval page), the plugin’s REST proxy fetches the verified result from <code>https://qrauth.io/api/v1/auth-sessions/verify-result</code>. The response carries the QRAuth user identifier and, when the <code>email</code> scope is allowed in Settings → QRAuth, the user’s email address. The plugin uses this only to locate or create the matching WordPress user; nothing beyond a hashed link reference is retained.</li>
<li>Hosted approval page — when a visitor on a phone taps “Continue with QRAuth”, the browser navigates to <code>https://qrauth.io/a/<token></code> to complete the social-provider flow. This is a standard cross-domain navigation initiated by the visitor.</li>
</ul>
The vendored web component (<code>assets/js/qrauth-components.js</code>) is served from your own WordPress site — there is no third-party JavaScript on wp-login.php, and the component does not contact qrauth.io directly from the browser; all server-to-server calls are proxied via your site’s REST API.
Service terms and policies
<ul>
<li>Terms of Service: https://qrauth.io/terms</li>
<li>Privacy Policy: https://qrauth.io/privacy</li>
<li>Data Processing Addendum: https://qrauth.io/dpa</li>
<li>List of Sub-processors: https://qrauth.io/subprocessors</li>
</ul>
<h3>Source</h3>

The compiled bundle at <code>assets/js/qrauth-components.js</code> carries the following banner header at the top of the file:
<pre><code>`
</code></pre>
/*! 
 * @qrauth/web-components v0.4.1 
 * Vendored by qrauth-passwordless-social-login. Do not edit by hand. 
 * 
 * Source: https://github.com/qrauth-io/qrauth/tree/main/packages/web-components 
 * License: MIT 
 * npm: https://www.npmjs.com/package/@qrauth/web-components 
 * Build: <code>npm install && npm run build:assets</code> (see bin/fetch-web-components.mjs) 
 * 
 * The unminified TypeScript source for this bundle is also vendored at 
 * assets/js/source/ — see assets/js/source/README.md for provenance. 
 */ 
 `
The unminified TypeScript source files are also vendored alongside the compiled bundle inside this plugin (<code>assets/js/source/</code>) for offline review.
The plugin’s own source — PHP, the small browser adapter (<code>assets/js/qrauth-adapter.js</code>), build scripts, tests, and CI — is publicly maintained under GPL-2.0-or-later at:
<ul>
<li>Plugin source repository: https://github.com/qrauth-io/qrauth-passwordless-social-login</li>
</ul>
The PHP and <code>assets/js/qrauth-adapter.js</code> shipped in the plugin ZIP are non-minified — read them directly without checking out the repo.
The vendored file <code>assets/js/qrauth-components.js</code> is a pinned production build of the public <code>@qrauth/web-components</code> library. The non-compiled source for that library is openly available:
<ul>
<li>Source repository: https://github.com/qrauth-io/qrauth/tree/main/packages/web-components (MIT-licensed)</li>
<li>npm release: https://www.npmjs.com/package/@qrauth/web-components — pinned to v0.4.1, sha512 in <code>package.json</code> under the <code>qrauth.webComponentsIntegrity</code> key</li>
<li>Build instructions for the upstream library: https://github.com/qrauth-io/qrauth/blob/main/BUILDING.md</li>
</ul>
To regenerate the vendored bundle from the pinned npm release, clone the plugin source repository linked above and run from its root:
<pre><code>npm install
npm run build:assets
</code></pre>
The build script <code>bin/fetch-web-components.mjs</code> (kept in the plugin source repository, not in the WordPress.org plugin ZIP) downloads the npm tarball, verifies its sha512 SRI hash against <code>package.json#qrauth.webComponentsIntegrity</code>, extracts the IIFE build, and writes it to <code>assets/js/qrauth-components.js</code>. CI runs the same script before the WordPress.org plugin-check job, so the bundle distributed on the directory always matches the published npm release. To rebuild from upstream source instead of the pinned tarball, follow <code>BUILDING.md</code> in the upstream library repository above.

QRAuth – Passwordless & Social Login

Passwordless sign-in for WordPress. Users scan a QR code with the QRAuth mobile app — no passwords, no forms, no OAuth apps to register.

Cozmoslabs

Cristian Antohe

Chris Martens

Transform your WordPress login experience with passwordless authentication. Users simply enter their email address and receive a secure magic link – click to login instantly. It’s more secure than weak passwords and infinitely more user-friendly.
<h4>Why Choose Keyless Auth?</h4>
<ul>
<li>Enhanced Security: No more weak, reused, or compromised passwords</li>
<li>Better User Experience: One click instead of remembering complex passwords</li>
<li>Reduced Support: Eliminate “forgot password” requests</li>
<li>Modern Authentication: Enterprise-grade security used by Slack, Medium, and others</li>
<li>Security Hardening: Built-in protection against brute force attacks and username enumeration</li>
</ul>
<h4>Quick Start</h4>
<ol>
<li>Install and activate the plugin</li>
<li>Create a new page and add the shortcode <code>[keyless-auth]</code></li>
<li>Configure email templates in Keyless Auth → Templates</li>
<li>Done! Users can now login passwordlessly</li>
</ol>
<h4>Core Features</h4>
Ready to Use 
* Magic Link Authentication – Secure, one-time login links via email 
* Two-Factor Authentication (2FA) – Complete TOTP support with Google Authenticator 
* Role-Based 2FA – Require 2FA for specific user roles (admins, editors, etc.) 
* Custom 2FA Setup URLs – Direct users to branded frontend 2FA setup pages 
* SMTP Integration – Reliable email delivery through your mail server 
* Email Templates – Professional, customizable login emails 
* Mail Logging – Track all sent emails with delivery status 
* Custom Database Tables – Scalable architecture with dedicated audit logs
Advanced Security 
* Token Security: 10-minute expiration, single-use tokens 
* Audit Logging: IP addresses, device types, login attempts 
* Emergency Mode: Grace period system with admin controls 
* Secure Storage: SMTP credentials in wp-config.php option 
* XML-RPC Disable: Block brute force attacks via XML-RPC interface 
* Application Passwords Control: Disable programmatic authentication when not needed 
* User Enumeration Prevention: Block username discovery attacks
Customization 
* WYSIWYG Email Editor: Full HTML support with live preview 
* Advanced Color Controls: Hex, RGB, HSL color formats 
* Template System: German, English, and custom templates 
* Branding Options: Custom sender names and professional styling
<h4>Installation & Setup</h4>
Basic Installation 
1. WordPress Admin → Plugins → Add New 
2. Search for “Keyless Auth” 
3. Install and activate 
4. Add [keyless-auth] shortcode to any page
SMTP Configuration (Recommended) 
1. Navigate to Keyless Auth → SMTP 
2. Configure your email provider (Gmail, Outlook, SendGrid, etc.) 
3. Test email delivery 
4. Save settings
Two-Factor Authentication Setup 
1. Go to Keyless Auth → Options 
2. Enable “Two-Factor Authentication” 
3. Select required user roles 
4. Users scan QR code with authenticator app
<h4>Email Templates</h4>
Template Options 
* German Professional: Sleek German-language template 
* English Simple: Clean, minimalist design 
* Custom HTML: Create your own with WYSIWYG editor
Customization Features 
* Full HTML and CSS support 
* Color picker for buttons and links 
* Responsive email design 
* Live template preview 
* Placeholder system for dynamic content
<h4>Security & Compliance</h4>
Token Security 
* Generated using WordPress security standards 
* Based on user ID, timestamp, and wp-config.php salt 
* 10-minute expiration with single-use enforcement 
* Secure database storage with automatic cleanup
Two-Factor Authentication 
* TOTP-based system compatible with Google Authenticator, Authy 
* Role-based requirements for granular control 
* Grace period system for smooth user transitions 
* Custom verification forms with professional styling
Database Architecture 
* Custom tables for optimal performance 
* Comprehensive audit logging 
* Device tracking and IP monitoring 
* Automatic maintenance and cleanup routines
<h4>Security Hardening</h4>
Keyless Auth includes comprehensive security hardening features to protect your WordPress site from common attack vectors. All features are optional and can be enabled based on your site’s needs.
XML-RPC Disable 
* Prevents brute force attacks via WordPress XML-RPC interface 
* Reduces attack surface by disabling legacy API 
* Recommended for sites not using Jetpack, mobile apps, or pingbacks
Application Passwords Control 
* Disable REST API and XML-RPC authentication when programmatic access isn’t needed 
* Prevents unauthorized API access 
* Recommended for simple sites without third-party integrations
User Enumeration Prevention 
* Blocks REST API user endpoints (<code>/wp-json/wp/v2/users</code>) 
* Redirects author archives and <code>?author=N</code> queries 
* Removes login error messages that reveal usernames 
* Strips comment author CSS classes 
* Removes author data from oEmbed responses 
* Recommended for business/corporate sites without author profiles
Benefits 
* Combined protection against brute force attacks 
* Prevents username discovery for targeted attacks 
* Reduces unauthorized API access 
* Easy to configure without code or .htaccess modifications 
* All features include comprehensive documentation 
* FTP recovery available if needed
<h4>SMTP & Email Delivery</h4>
Supported Providers 
* Gmail / Google Workspace 
* Outlook / Microsoft 365 
* Mailgun, SendGrid, Amazon SES 
* Any SMTP-compatible service
Advanced Email Features 
* Message-ID domain alignment for deliverability 
* SPF/DKIM/DMARC compliance 
* Custom sender names and addresses 
* Bulk email log management 
* Delivery status tracking
Secure Credential Storage 
Store SMTP credentials securely in wp-config.php:
<pre><code>define('CHRMRTNS_KLA_SMTP_USERNAME', 'your-email@example.com');
define('CHRMRTNS_KLA_SMTP_PASSWORD', 'your-smtp-password');
</code></pre>
<h4>WordPress Integration</h4>
Login Page Integration 
* Optional magic login field on wp-login.php 
* Seamless integration with existing login flow 
* Toggle control for easy enable/disable 
* Clean, responsive form styling
Shortcode Usage 
Use <code>[keyless-auth]</code> anywhere: pages, posts, widgets, or custom templates.
<h4>Developer Features</h4>
Hooks & Filters
Customize login redirect: 
 add_filter(‘wpa_after_login_redirect’, ‘custom_redirect_function’);
Modify email headers: 
 add_filter(‘wpa_email_headers’, ‘custom_email_headers’);
Change token expiration: 
 add_filter(‘wpa_change_link_expiration’, ‘custom_expiration_time’);
Modular Architecture 
* Clean, organized class structure 
* Separated concerns for easy maintenance 
* WordPress coding standards compliance 
* Extensive documentation and comments
<h4>Requirements</h4>
<ul>
<li>WordPress: 3.9 or higher (tested up to 6.8)</li>
<li>PHP: 7.4 or higher</li>
<li>Email Delivery: SMTP recommended for reliability</li>
</ul>
Note: Keyless Auth complements WordPress’s default login system – it doesn’t replace it.
Developed by Chris Martens | Based on the original Passwordless Login plugin by Cozmoslabs

Keyless Auth – Login without Passwords

Secure, passwordless authentication for WordPress. Your users login via magic email links – no passwords to remember or forget.

QRAuth – Passwordless & Social Login vs Keyless Auth – Login without Passwords