Passkeys depend 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.
HTTPS and Secure Contexts
Production sites should use HTTPS. WebAuthn requires a secure context. A site that is served insecurely over normal HTTP should not be treated as a valid production Passkey setup.
Browsers commonly make special allowances for local development hosts, but those exceptions should not be used as evidence that a public HTTP site is correctly configured.
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 behavior.
- 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
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? Because browser Passkey support changes over time, use this page as the configuration baseline and test the browsers and devices your audience actually uses.
