Applies to: Free and Pro · Location: VentraConnect → Diagnostics
Passkeys depend on server requirements and on WebAuthn support in the browser, operating system and authenticator. VentraConnect provides the WordPress integration, but the credential-creation and verification interface comes from the user’s environment.
Server requirements
json, openssl and mbstring are required. gmp or bcmath is recommended.The Passkeys section of VentraConnect Diagnostics shows whether your PHP version supports passkeys and whether the Passkey method is enabled:
For the requirements of the other login methods, see Requirements & compatibility.
HTTPS and secure contexts
Production sites must use HTTPS. Browsers only allow passkeys (WebAuthn) in a secure context. A public site served over plain HTTP should not be treated as a valid passkey setup.
Browsers accept http://localhost for local testing. Do not treat that exception as evidence that a public HTTP site is correctly configured.
Passkeys are tied to your site’s domain. Only the exact origin (scheme, host and port) of your WordPress Address is accepted. Passkeys created on a staging domain, or before a domain change, will not work on the new domain: users must add new ones.
Browser and device support
Modern versions of the major browsers and operating systems generally support WebAuthn, but the exact passkey experience varies.
| Environment | Typical passkey experience |
|---|---|
| Windows | Windows Hello, compatible password managers, phones, or hardware security keys depending on browser and system setup. |
| macOS | Touch ID or other platform credentials, compatible password managers, phones, or security keys. |
| iPhone / iPad | Platform passkeys through the supported Apple authentication experience, subject to browser and account configuration. |
| Android | Device authentication, supported password managers, or other available WebAuthn authenticators. |
| Linux | Browser support with compatible password managers, external authenticators, or hardware security keys; availability varies more by desktop setup. |
Compatible authenticators
- Windows Hello
- Touch ID and supported Apple platform authentication
- Android device biometrics
- Compatible password managers that support passkeys
- FIDO2/WebAuthn hardware security keys
- Cross-device authentication where offered by the browser
Common compatibility limits
- Old browsers or operating systems may not expose the WebAuthn capabilities VentraConnect needs.
- Embedded browsers and in-app webviews can behave differently from full desktop or mobile browsers.
- Private browsing can change how browsers expose synced credentials, although it remains useful for testing logged-out behaviour.
- Remote desktops, virtual machines, and restricted enterprise devices may not expose the same authenticators as a normal local session.
- Security software, browser policies, or managed-device policies may restrict WebAuthn features.
Recommended compatibility test
Work through these in order:
- Check the server. Confirm PHP 8.2+ and the required extensions in VentraConnect Diagnostics.
- Verify HTTPS. Confirm the public site loads securely without certificate warnings.
- Use a current browser. Test with at least one browser representative of your real users.
- Register a passkey. Confirm the browser offers an authenticator and VentraConnect completes registration.
- Log out completely. Use a private or incognito window if needed.
- Test passkey login. Confirm authentication works and redirects correctly.
- Test a fallback. Make sure users still have an appropriate recovery method for your rollout stage.
Need exact browser-version guidance? Browser passkey support changes over time, so use this page as the configuration baseline and test the browsers and devices your audience actually uses. For help with specific errors, see Troubleshooting Passkeys.
