SIMPLE JWT LOGIN
Simple JWT Login – Allows you to use JWT on REST endpoints. translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Simple JWT Login – Allows you to use JWT on REST endpoints. does, but does not yet establish specific visitor-facing content values that REEID should translate.
Visit Simple JWT Login – Allows you to use JWT on REST endpoints. ↗
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
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).
Distinctive features
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).
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what Simple JWT Login – Allows you to use JWT on REST endpoints. does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
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.
Does the current evidence establish translation scope for Simple JWT Login – Allows you to use JWT on REST endpoints.?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.