Daniel Bachhuber

Ryan McCue

Joe Hoyle

Rachel Baker

<p>Used together with the <a href="https://github.com/WP-API/OAuth1" rel="nofollow ugc">WP REST API OAuth 1.0a Server plugin</a>, this allows <a href="https://apps.wp-api.org/" rel="nofollow ugc">the WP RET API Authentication Broker</a><br />
to connect to your site.</p>
<p>Read about how it works <a href="https://apps.wp-api.org/" rel="nofollow ugc">on the reference broker</a>, or <a href="https://apps.wp-api.org/spec/" rel="nofollow ugc">read the full specification</a>.</p>


WordPress REST API – Authentication Broker

Used together with the WP REST API OAuth 1.0a Server plugin, this allows the WP RET API Authentication Broker

hectavex

<p>New providers and features are being added regularly! See the <a href="https://wordpress.org/plugins/wp-oauth/changelog/" rel="ugc">Changelog</a> for details.</p>
<p>As a reminder, WP-OAuth is a still a pre-v1.0 release, which means some features may not work as intended or might change over time. Please report any bugs/issues to the support forum so they can be fixed as soon as possible. Thank you!</p>
<h4>Facts</h4>
<ul>
<li>With so many sites offering membership now, users may suffer registration fatigue and forget their passwords, or use the same password for several sites, increasing their security risk.</li>
<li><a href="http://www1.janrain.com/rs/janrain/images/Industry-Research-Value-of-Social-Login-2013.pdf" rel="nofollow ugc">56% of consumers</a> have at least one major social network profile they could be using for membership, registration and login purposes across multiple websites without having to maintain multiple accounts and passwords (2013).</li>
<li><a href="http://www.marketingprofs.com/charts/2012/7060/social-media-users-prefer-social-login-over-traditional" rel="nofollow ugc">40% of consumers</a> currently utilize social login (2012).</li>
</ul>
<h4>Features</h4>
<ul>
<li>Free, unlimited, unbranded and white-labeled from the beginning. No upselling, no payment plans, no SaaS, no proxy authentication! WP-OAuth communicates from your WordPress site <em>directly</em> with the <em>trusted</em> third-party login providers.</li>
<li>WP-OAuth collects and stores ONLY the user’s <em>OAuth identity</em> in the WordPress database for future logins; no other user information is collected or stored.</li>
<li>Fully integrates with WordPress. Drops into existing WordPress sites and integrates with existing WordPress users.</li>
<li>Supports third-party authentication with Google, Facebook, LinkedIn, Github, Reddit, Windows Live, PayPal and Instagram via OAuth 2.0 / OpenID Connect. Providers can be enabled or disabled.</li>
<li>Automatic user registration if <em>Anyone can register</em> has been enabled under Settings > General > Membership.</li>
<li>Users can manage their third-party login providers via the standard “Your Profile” WordPress page. They may link more providers, or unlink existing providers.</li>
<li>Displays a message via Javascript to the user when they login or logout. This feature can also be disabled.</li>
<li>Add a custom login form to any post or page using the [wpoa_login_form] shortcode. Choose from 4 different layouts. See <a href="https://wordpress.org/plugins/wp-oauth/installation/" rel="ugc">Installation</a> for details.</li>
<li>Customize the default login screen with a logo or background. Point the logo URL to your home page instead of WordPress.org. Hide the default username/password login form if you want. Automatically include login buttons for any providers that are enabled.</li>
<li>Supports cURL or stream context for the authentication flow, meaning the plugin should be compatible with a wide range of PHP servers.</li>
<li>The authentication flow was adapted from code samples provided by Google, Facebook and LinkedIn. It has been updated, rigorously tested and debugged for solid error handling. Provider implementations share much of the same code (very high code re-use) and the differences between the providers have been fully documented.</li>
<li>The user experience and on-boarding process was inspired by StackExchange/StackOverflow login system.</li>
<li>Extremely light-weight, optimized code base for high performance. Doesn’t require third-party OAuth libraries; everything is built first-class into the plugin. Previously, WP-OpenLogin required LightOpenID and Facebook-PHP-SDK, but this is no longer necessary. Keeps the bloat low and the performance high. Tested with P3 Plugin Profiler, WP-OAuth’s plugin overhead is around 0.001 seconds which is 6x less overhead than Akismet in the same run! That means there shouldn’t be a performance hit.</li>
</ul>
<h4>How to Contribute</h4>
<p>Visit the <a href="https://github.com/perrybutler/WP-OAuth" rel="nofollow ugc">GitHub development repository</a>.</p>
<h3>History</h3>
<p>This project is a continuation of <a href="http://github.com/perrybutler/wp-openlogin" rel="nofollow ugc">WP-OpenLogin</a> which was originally developed with OpenID in mind. We’re moving on; OAuth 2.0 is now the standard.</p>


WP-OAuth

Allows users to login or register by authenticating with an existing Google, Facebook, LinkedIn, Github, Reddit (and more!) account via OAuth 2.0.

WordPress REST API – Authentication Broker vs WP-OAuth