Àpèjúwe
ZapQR Login gives your WordPress site passwordless sign-in, two ways:
Sign in with ZapQR (SSO) — recommended
A “Sign in with ZapQR” button on your login page. Visitors sign in with their ZapQR account — passkey-first (Face ID / Touch ID / security key), with an email link as fallback — via standards-based OpenID Connect single sign-on. One ZapQR account works across every site that offers it.
- Passkey-first: phishing-resistant WebAuthn sign-in, no passwords anywhere
- Standards-based: OAuth 2.0 authorization-code flow with PKCE; ID tokens verified in the plugin (RS256, JWKS)
- Links existing WordPress users by their verified email — admins keep their role
- New visitors are created with a low-privilege role you choose (Subscriber by default)
- Single logout: logging out of WordPress also ends the ZapQR session
- No external code: the whole flow is server-side redirects and server-to-server calls
QR credential fill (classic)
Users save their WordPress credentials in the ZapQR app; on the login page they scan a QR code and the login form fills and submits itself. Credentials travel phone browser over an encrypted WebSocket relay and are never stored on external servers.
External services
This plugin talks to the following services. No data is sent anywhere until a site administrator enables the relevant mode.
ZapQR identity provider (SSO mode) — auth.zapqr.ai by default, or a self-hosted issuer the admin configures. When a visitor clicks “Sign in with ZapQR” their browser is redirected there to authenticate; your server then exchanges an authorization code (server-to-server) and receives the visitorÌtumọ̀ Yorùbá: ’s email address and its verified status — nothing else. Provider: DaSecure (zapqr.ai, terms and privacy linked there).
ZapQR relay (QR mode) — wss://relay.zapqr.ai, a WebSocket relay that pairs the login page with the visitorÌtumọ̀ Yorùbá: ’s phone using a random session identifier. Credentials pass through end-to-end encrypted and are not stored. Provider: DaSecure (zapqr.ai).
QR image service (QR mode) — api.qrserver.com renders the QR image. It receives only the random session identifier and your siteÌtumọ̀ Yorùbá: ’s hostname — never credentials. Provider: goqr.me (privacy).
Àwọn àwòrán ìbòjú
Ìgbéwọlẹ̀
- Install and activate the plugin.
- For SSO: go to Settings > ZapQR Login, copy the Redirect URI and Post-logout URI shown there, register your site at the ZapQR identity provider to get a Client ID and Secret, paste them in, tick Enable, save.
- For QR fill: nothing to configure — the widget appears on wp-login.php. Customize theme and accent color in Settings > ZapQR Login.
FAQ
-
What does the site receive about the visitor in SSO mode?
-
Only a verified email address and a stable account identifier, delivered in a cryptographically signed token that the plugin verifies against the providerÌtumọ̀ Yorùbá: ’s published keys. No passwords, no passkeys, no profile data.
-
Can someone take over an existing account?
-
No. Linking to an existing WordPress user happens only when the ZapQR identity provider asserts the email is verified; unverified emails are rejected outright. You can also disable linking entirely, and new users always get the low-privilege role you configure.
-
Where do passkeys live?
-
With the visitor and the ZapQR identity provider — never on your WordPress site. Your site only consumes the signed sign-in assertion.
-
Does the QR credential mode still work?
-
Yes, unchanged. It is a separate, coexisting mode: the ZapQR app stores per-site WordPress credentials locally on the phone (Face ID / Touch ID protected) and relays them to the browser at login.
-
Does this work with multisite?
-
Yes.
Àwọn àgbéyẹ̀wò
Kò sí àwọn àgbéyẹ̀wò fún plugin yìí.
Àwọn Olùkópa & Olùgbéejáde
“ZapQR Login” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin yìí.
Àwọn Olùkópa
Túmọ̀ “ZapQR Login” sí èdè rẹ.
Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè?
Ṣàwárí koodu, ṣàyẹ̀wò ibi ìpamọ́ SVN, tàbí ṣe àgbékalẹ̀ sí àkọsílẹ̀ ìdàgbàsókè nípasẹ̀ RSS.
Àkọsílẹ̀ àwọn àyípadà
1.2.0
- New: back-channel logout. Register the URI shown in Settings at ZapQR and signing out of ZapQR (or an Emergency sign-out) ends the WordPress session too — only the session that ZapQR session created.
- Fixed: single logout remembered one ID token per user, so after logging out on one device the next deviceÌtumọ̀ Yorùbá: ’s logout skipped ZapQR entirely. Each WordPress session now carries its own.
- Fixed: when ZapQR could not be reached at logout, the WordPress-only logout was silent; it is now logged.
- Fixed: Chrome could autofill the WordPress adminÌtumọ̀ Yorùbá: ’s saved username and password into Client ID and Client secret. The fields no longer look like a login form, and a Client ID that doesnÌtumọ̀ Yorùbá: ’t start with “zq_” gets a warning on save.
1.1.1
- Fixed: the QR widget showed a stale, unscannable code after a login was delivered (e.g. after logging out and back in). It now refreshes its session automatically after every successful fill.
- New:
window.ZapQR.refresh()lets themes/plugins request a fresh QR programmatically.
1.1.0
- New: “Sign in with ZapQR” single sign-on (OpenID Connect, authorization-code + PKCE, RS256 ID-token verification via JWKS)
- New: link existing users by verified email; configurable default role for new users; optional single logout through the identity provider
- Changed: the QR widget script is now bundled with the plugin instead of loaded from zapqr.ai
- Hardened: explicit sanitization on all settings
1.0.0
- Initial release: QR code credential fill on wp-login.php, theme and accent customization