WP SAML AUTH
WP SAML Auth translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what WP SAML Auth does, but does not yet establish specific visitor-facing content values that REEID should translate.
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
- Provides SAML authentication for WordPress using either the bundled OneLogin SAML library or an optionally installed SimpleSAMLphp library.
- Adds a SAML login button to the standard WordPress login view.
- Redirects authenticated users back to WordPress and signs them in to their account.
- Can automatically create a new WordPress user when no matching account exists.
- Can log users out of the identity provider when they log out of WordPress.
- Supports configuration through a WordPress backend settings page or through filter-based code configuration.
- Includes WP-CLI commands under the `wp saml-auth` namespace.
- Can auto-detect SimpleSAMLphp installations in common paths and supports both v1.x and v2.x autoloaders.
Distinctive features
SAML authentication for WordPress with support for either the bundled OneLogin SAML library or an optionally installed SimpleSAMLphp library. Includes login-page SAML access, optional user creation, identity-provider logout handling, backend and code-based configuration, and WP-CLI commands.
Dynamic content
Documented dynamic behavior includes SAML sign-in flow, account creation when no matching user exists, and logout handling with the identity provider. No broader runtime content behavior is established by the supplied evidence.
SEO and metadata
No SEO or metadata behavior is established by the supplied evidence.
URLs and navigation
The plugin redirects authenticated users back to WordPress after SAML sign-in. No broader URL handling or navigation behavior is established by the supplied evidence.
Forms and commerce
No forms or commerce behavior is established by the supplied evidence.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what WP SAML Auth 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
- Evidence is limited to documented SAML login, logout, provisioning, configuration, WP-CLI, and SimpleSAMLphp detection behavior. Additional compatibility details are not established by the supplied evidence. The plugin’s behavior on other WordPress surfaces is not documented here.
COMMON QUESTIONS
WP SAML Auth and REEID Translate FAQ.
Does the current evidence establish translation scope for WP SAML Auth?
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.