
AUTHENTRY
Authentry – Face ID, Fingerprint & Passkey Login compatibility with REEID Translate
Authentry – Face ID, Fingerprint & Passkey Login compatibility with REEID Translate is being reviewed using official plugin documentation. FIDO2/WebAuthn compliant passwordless authentication supporting platform (Face ID, Touch ID, Windows Hello) and roaming authenticators No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Authentry – Face ID, Fingerprint & Passkey Login does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Authentry – Face ID, Fingerprint & Passkey Login is documented in the Security category with 7 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How Authentry – Face ID, Fingerprint & Passkey Login compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- FIDO2/WebAuthn compliant passwordless authentication supporting platform (Face ID, Touch ID, Windows Hello) and roaming authenticators
- Usernameless login capability with automatic account discovery and fallback to standard email/username flow
- WooCommerce integration providing passkey buttons on login/register forms and a Security Keys management tab in My Account
- Replay attack protection via strictly enforced sign counts per credential and single-use cryptographic challenges
- Transient-based rate limiting for authentication requests (10 requests per IP per minute)
- Developer extensibility through WordPress hooks, filters, REST API endpoints, and shortcode-based UI placement
- Administrative and user-level passkey management allowing view, rename, and delete operations from WP Admin or frontend profiles
TRANSLATION BOUNDARY
Authentry – Face ID, Fingerprint & Passkey Login capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility. No specific content shown to visitors is confirmed for translation in this category.
FREQUENTLY ASKED QUESTIONS
Authentry – Face ID, Fingerprint & Passkey Login and REEID Translate FAQ.
What does Authentry – Face ID, Fingerprint & Passkey Login do?
Authentry – Face ID, Fingerprint & Passkey Login has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does Authentry – Face ID, Fingerprint & Passkey Login have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from Authentry – Face ID, Fingerprint & Passkey Login?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate Authentry – Face ID, Fingerprint & Passkey Login in a multilingual WordPress workflow.
REEID documents Authentry – Face ID, Fingerprint & Passkey Login functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.