Digitaldive

<p>WP OAuth2 adds “Login with WordPress.com” (OAuth2) to your WordPress login screen and a connect/disconnect widget on user profile pages. It’s designed for agencies and teams managing multiple sites who want a consistent WordPress.com login without installing Jetpack.</p>
<p>External Service: WordPress.com OAuth2 API<br />
– Service purpose: Authenticate users with their WordPress.com accounts.<br />
– Data sent: Client ID, redirect URI, OAuth authorization code, and standard HTTP request metadata during the OAuth flow.<br />
– Data received: WordPress.com user ID, email, and display name to link or create WordPress users.<br />
– Service terms: https://wordpress.com/tos/<br />
– Privacy policy: https://automattic.com/privacy/</p>
<p>Features:</p>
<ul>
<li>WordPress.com login (OAuth2 “auth” scope).</li>
<li>Link or unlink WordPress users to WordPress.com accounts.</li>
<li>Auto-create users when no matching email exists (optional).</li>
<li>Allowlist by email domain or WordPress.com user ID (optional).</li>
<li>Audit log of the last 20 OAuth attempts (optional).</li>
<li>Stores only WordPress.com user ID in user meta (no access tokens stored).</li>
<li>Short-lived OAuth state with HttpOnly cookie + transient for CSRF protection.</li>
</ul>
<p>Setup requires creating a WordPress.com application and adding the redirect URI shown in the plugin settings. Feature toggles let you enable or disable the login button, profile widget, auto-create users, admin notices, allowlists, and the audit log.</p>
<h3>Privacy</h3>
<p>This plugin connects to WordPress.com to authenticate users. It stores the WordPress.com user ID in WordPress user meta to link accounts. OAuth access tokens are used during the login flow and are not stored. A short-lived HttpOnly cookie and transient are used for OAuth state validation and expire automatically. If the audit log is enabled, the last 20 OAuth attempts are stored (time, status, IP address, and basic details) in a non-autoloaded option. WordPress.com service terms: https://wordpress.com/tos/ and privacy policy: https://automattic.com/privacy/.</p>


OAuth2 Account Login

Add WordPress.com OAuth2 login to WordPress. Let teams sign in with WordPress.com, link accounts, and avoid Jetpack. Not affiliated with Automattic.

Justin Greer

Jayson T Cote

<p>Connect your app to WordPress or use SSO to connect multiple websites with the same username and passwords. No 3rd party servers are needed with WP OAuth Server. Everything you need is in this plugin.</p>
<span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/ZOUsY4Kp_6U?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span>
<h4>Features</h4>
<ul>
<li>WP REST API Authentication. Provides ability to make authorized calls to protected REST API endpoints.</li>
<li>WP REST API Lock Down. Prevent any calls to the REST API unless authorized</li>
<li>Unlimited OAuth 2.0 Clients</li>
<li>Support for Implicit Flow</li>
<li>Built-In Resource Server</li>
<li>Automated Authorization Flow (User does not have to see authorization screen)</li>
<li>Easily Extend/ Modify the Endpoints</li>
<li>OAuth 2.0 PKCE</li>
<li>Modern and Legacy JWT authorization support. OAuth 2.0 JSON Web Token Support</li>
</ul>
<h4>Supported Grant Types</h4>
<ul>
<li>Authentication Code w/Implicit</li>
<li>User Credentials (Pro)</li>
<li>Client Credentials (Pro)</li>
<li>Refresh Token (Pro)</li>
<li>OpenID Connect (Pro)</li>
<li>OpenID Discovery</li>
<li>Public Clients (Pro)</li>
<li>Public Client Proof of Key Exchange (PKCE)</li>
</ul>
<h4>Supports</h4>
<ul>
<li>Connecting any Custom Mobile and Desktop Application to WordPress’s Backend.</li>
<li>Any software or web platform utilizing OAuth 2.0.</li>
<li>Allows RocketChat to use WordPress as a Backend.</li>
<li>Connects Moodle LMS and use WordPress users.</li>
<li>Alexa Skills Authentication</li>
<li>Tribe.so Community OAuth 2 SSO Support</li>
</ul>
<h4>How to Use</h4>
<p>Visit https://wp-oauth.com/support/documentation/ for detailed documentation on installing, configuring and using<br />
WordPress OAuth Server.</p>
<h4>Licensing</h4>
<p>WP OAuth Server is free to use. Please support the project by licensing. You can view more information at<br />
https://wp-oauth.com.</p>
<h4>Minimum Requirements</h4>
<ul>
<li>PHP 5.6.4 or greater <em>(latest version recommended)</em></li>
<li>OpenSSL installed and enabled if you plan on using OpenID Connect</li>
</ul>
<h4>Other Information</h4>
<ul>
<li>NOTE: As of 3.0.0, there are no backward compatibility for any version older than 3.0.0</li>
<li>NOTE: Due to IIS’s inability play nice, WP OAuth Server may work but is very limited for Windows OS.</li>
</ul>
<h4>Support</h4>
<p>Support requests should be made by opening a support request at https://wp-oauth.com/support/submit-ticket/.</p>


WP OAuth Server (OAuth Authentication)

There is no answer even on the premium version website. The plugin is abandoned, with legacy code and some bugs. Please, choose an alternative decision. Didn't use this one!

Abandoned plugin


I just want to say thank you to the developer, you have done a great job and saved me a tonne of time :)


This plugin is really fantastic


I tested WP OAuth Server (OAuth Authentication) in integration with a client application and found a serious issue: even after the user logs out from WordPress, the issued access token is still accepted by the /oauth/me endpoint, returning all user data.



This means any client application that has stored the token can continue accessing private information indefinitely, until the token expires, without verifying if the session on the server has ended.



I tried to work around the issue by enabling the introspection endpoint and validating the token on each request, but the plugin does not revoke the token on logout, making introspection ineffective for detecting logouts.



This flaw breaks a basic security principle of OAuth 2.0 and may expose sensitive data. I do not recommend using this plugin until token revocation upon logout is implemented.


Serious security flaw — tokens remain valid after logout

Adds Authentication through OAuth 2. Provides the ability for Single Sign On for websites & Mobile Applications.

OAuth2 Account Login vs WP OAuth Server (OAuth Authentication)