SIMPLE JWT LOGIN
Simple JWT Login – Allows you to use JWT on REST endpoints. compatibility with REEID Translate
Simple JWT Login – Allows you to use JWT on REST endpoints. compatibility with REEID Translate is being evaluated from available plugin evidence. JWT-based authentication for WordPress REST endpoints, including validating a JWT against a configured “JWT Decryption key” and “JWT Decryption algorithm”. No specific visitor-facing translation surface is currently confirmed.
Visit Simple JWT Login – Allows you to use JWT on REST endpoints. ↗
AWAITING VERIFICATION
What the available evidence establishes for Simple JWT Login – Allows you to use JWT on REST endpoints..
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Simple JWT Login – Allows you to use JWT on REST endpoints. is documented in the Security category with 8 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Simple JWT Login – Allows you to use JWT on REST endpoints. compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- JWT-based authentication for WordPress REST endpoints, including validating a JWT against a configured “JWT Decryption key” and “JWT Decryption algorithm”.
- Auto-login support where the plugin extracts user identity (email and/or user ID) from a specified key in the JWT payload; JWT can be supplied via URL, Authorization header, cookie, or session (with precedence/overwrite behavior when multiple are present).
- REST API routes for authentication lifecycle operations: generating JWTs via an `/auth` endpoint, refreshing via an `auth/refresh` route, validating via `auth/validate`, and revoking via `auth/revoke`.
- Optional “protect endpoints” capability to require JWT for REST endpoints (either all REST endpoints with a whitelist, or only specific endpoints), returning an authorization error response when JWT is not provided.
- Optional “auth codes” layer that can be required for auto-login/register/delete flows, described as containing an authentication key, a role component, and an expiration date (or non-expiring if left blank).
- Access-control constraints for sensitive actions: auto-login/register/delete can be limited to specific client IP addresses; user registration can be limited to specific email domains; delete-user and reset-password/change-password endpoints are described as disabled by default and can be enabled/configured.
- User management endpoints/actions tied to JWT: register new users via a POST request (with options like role selection and optional random password generation), delete users by user ID or email based on configured JWT payload keys, and reset/change passwords via dedicated endpoints (disabled by default).
- CORS configuration for plugin routes and support for redirect behavior after auto-login (including optional redirect URL allowlisting and redirect variables derived from the logged-in user).
CONTENT BOUNDARY
Simple JWT Login – Allows you to use JWT on REST endpoints. capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Simple JWT Login – Allows you to use JWT on REST endpoints. and REEID Translate FAQ.
What does Simple JWT Login – Allows you to use JWT on REST endpoints. do according to the available plugin evidence?
Simple JWT Login – Allows you to use JWT on REST endpoints. has 8 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Simple JWT Login – Allows you to use JWT on REST endpoints.?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Simple JWT Login – Allows you to use JWT on REST endpoints.?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Simple JWT Login – Allows you to use JWT on REST endpoints. in a multilingual WordPress workflow.
REEID documents Simple JWT Login – Allows you to use JWT on REST endpoints. functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.