Elementor

<p>Sticklight Connector provides a structured way to use the WordPress user system in external or React-based applications.</p>
<p>The plugin extends the WordPress REST API with additional endpoints that allow authenticated clients to retrieve user context and interact with WordPress data, while fully respecting core authentication methods, roles, and capability checks.</p>
<p>Sticklight does not replace WordPress authentication. It relies on <code>wp_authenticate</code> for credential validation and WordPress Application Passwords for API access, and follows standard permission checks (<code>current_user_can</code>) for all requests.</p>
<h4>Typical use cases</h4>
<ul>
<li>React applications connected to a WordPress site</li>
<li>Headless or hybrid WordPress setups</li>
<li>Admin or user dashboards built outside wp-admin</li>
<li>External tools that require authenticated access to WordPress data</li>
</ul>
<h4>Features</h4>
<ul>
<li>Authenticates via <code>wp_authenticate</code> and issues Application Passwords for API access</li>
<li>Adds REST endpoints for login, logout, and retrieving current user context</li>
<li>Enforces WordPress capability checks on all requests</li>
<li>Supports cross-origin headless setups</li>
<li>Extensible via WordPress hooks and filters</li>
</ul>
<h3>Usage</h3>
<h4>Login</h4>
<p>Authenticate with username (or email) and password:</p>
<pre><code>POST /wp-json/sticklight/v1/auth/login
</code></pre>
<p>On success the response includes an Application Password for subsequent API requests and the authenticated user:</p>
<pre><code>{
  "app_password": "XXXX XXXX XXXX XXXX XXXX XXXX",
  "user": {
    "user_id": 1,
    "username": "admin",
    "display_name": "Admin",
    "email": "admin@example.com",
    "roles": ["administrator"]
  }
}
</code></pre>
<p>Use the returned <code>app_password</code> with HTTP Basic Authentication for all further requests.</p>
<h4>Current user</h4>
<p>Retrieve the current authenticated user:</p>
<pre><code>GET /wp-json/sticklight/v1/auth/me
</code></pre>
<h4>Logout</h4>
<p>Revoke the current Application Password session:</p>
<pre><code>POST /wp-json/sticklight/v1/auth/logout
</code></pre>
<h4>User registration</h4>
<p>User creation is handled through the built-in WordPress REST API (<code>POST /wp-json/wp/v2/users</code>) and requires administrator authentication.</p>
<h4>Accessing protected data</h4>
<p>Requests to any endpoint must pass standard WordPress permission checks. Sticklight does not bypass or override these checks.</p>
<h3>Security</h3>
<p>Sticklight follows WordPress security practices:</p>
<ul>
<li>Authenticates via <code>wp_authenticate</code>, which respects all security plugin hooks (rate limiting, two-factor authentication, brute-force protection)</li>
<li>Issues Application Passwords scoped to individual sessions</li>
<li>Does not provide user registration — accounts must be created by an administrator</li>
<li>Applies capability checks (<code>current_user_can</code>) on all endpoints</li>
<li>Does not expose private data without proper permissions</li>
</ul>
<p>For external applications, it is recommended to:</p>
<ul>
<li>Use HTTPS</li>
<li>Restrict allowed origins</li>
<li>Avoid exposing sensitive endpoints unnecessarily</li>
</ul>


Sticklight

Use WordPress authentication and permissions in external React applications via secure REST API endpoints.

Dropndot Solutions

droptheme

<p>Frontend View For Headless CMS is a plugin that seamlessly links your backend WordPress content, including posts, pages, custom post types, taxonomies, categories, and authors to your headless CMS frontend site. This ensures that any content in your WordPress backend are linked with your headless CMS frontend, therefore, you can easily visit the contents using visit links.</p>
<p><strong>Features:</strong></p>
<ul>
<li>Set your headless frontend base URL in <strong>Frontend View Settings</strong>.</li>
<li>Rewrite <strong>View</strong> links on post, page, CPT, taxonomy, and user list screens.</li>
<li>Optional custom <strong>preview path</strong> (for example <code>/preview/post-slug/</code>) for draft and preview links.</li>
<li>Map <strong>author</strong> archive paths to your frontend user segment.</li>
<li>Per-taxonomy and per–post-type <strong>slug overrides</strong> to match your frontend routes.</li>
<li><strong>Empty slug</strong> option to remove taxonomy or CPT base segments from generated URLs (for flat routes like <code>/my-post/</code> instead of <code>/products/my-post/</code>).</li>
<li>Frontend links in wp-admin open in a <strong>new tab</strong> for safer editing workflows.</li>
<li><strong>Settings</strong> shortcut on the Plugins screen for quick access to configuration.</li>
<li>Redesigned settings page with slug mapping UI, quick guide, and helpful resources.</li>
</ul>
<p>Works with any frontend that consumes WordPress via the REST API, GraphQL, or your own data layer—as long as your frontend URLs follow the paths you configure.</p>
<h3>Development</h3>
<p>This plugin is developed by Dropndot Solutions. For more information, visit <a href="https://www.dropndot.com/" rel="nofollow ugc">Dropndot Solutions</a>.</p>
<h3>Contact</h3>
<p>For support or inquiries, please contact us at <a href="mailto:info@dropndot.com" rel="nofollow ugc">info@dropndot.com</a>.</p>
<h3>Like the Plugin?</h3>
<p>If you find this plugin helpful, please leave a positive review on the <a href="https://wordpress.org/plugins/frontend-view-for-headless-cms" rel="ugc">WordPress Plugin Directory</a></p>


Frontend View For Headless CMS


Great plugin, it works for all the post types and even for users as well. I've used it in my React Project. The backend is Headless WordPress.


Great plugin, it works for all the post types and even for users as well.

Frontend View For Headless CMS links backend WordPress articles, pages, custom post types, taxonomies, and categories to the headless CMS site.

Sticklight vs Frontend View For Headless CMS