chingor13

<p>This plugin enables a resourceful REST interface for posts and comments.  Authentication is handled via the <a href="https://wordpress.org/extend/plugins/oauth-provider/" rel="ugc">oauth-provider plugin</a>.</p>
<p>For more information about resourceful routing, see <a href="http://guides.rubyonrails.org/routing.html" rel="nofollow ugc">here</a>.</p>
<p>Acceptable return formats:</p>
<ul>
<li>JSON</li>
</ul>
<p>Endpoints:</p>
<ul>
<li>GET – /api/posts.:format</li>
<li>GET – /api/posts/:id.:format</li>
<li>POST – /api/posts.:format</li>
<li>PUT – /api/posts/:id.:format</li>
<li>GET – /api/comments.:format</li>
<li>GET – /api/comments/:id.:format</li>
<li>POST – /api/comments.:format</li>
<li>PUT – /api/comments/:id.:format</li>
</ul>
<h3>To Do</h3>
<ol>
<li>Limit authentication to specific endpoints (customizable)</li>
</ol>


OAuthRest

OAuthRest is an implementation of a resourceful REST api.  It uses authentication via the oauth-provider plugin.

Automattic

WordPress.org

Alex Kirk

Ashish Kumar (Ashfame)

Paulo Pinto

<p>With this plugin you can use your own WordPress install to authenticate with a webservice that provides <a href="https://openid.net/connect/" rel="nofollow ugc">OpenID Connect</a> to implement Single-Sign On (SSO) for your users.</p>
<p>The plugin is currently only configured using constants and hooks as follows:</p>
<h3>Define the RSA keys</h3>
<p>If you don’t have keys that you want to use yet, generate them using these commands:</p>
<pre><code>openssl genrsa -out oidc.key 4096
openssl rsa -in oidc.key -pubout -out public.key
</code></pre>
<p>And make them available to the plugin as follows (this needs to be added before WordPress loads):</p>
<pre><code>define( 'OIDC_PUBLIC_KEY', <<<OIDC_PUBLIC_KEY
-----BEGIN PUBLIC KEY-----
...
-----END PUBLIC KEY-----
OIDC_PUBLIC_KEY
);

define( 'OIDC_PRIVATE_KEY', <<<OIDC_PRIVATE_KEY
-----BEGIN PRIVATE KEY-----
...
-----END PRIVATE KEY-----
OIDC_PRIVATE_KEY
);
</code></pre>
<p>Alternatively, you can also put them outside the webroot and load them from the files like this:</p>
<pre><code>define( 'OIDC_PUBLIC_KEY', file_get_contents( '/web-inaccessible/oidc.key' ) );
define( 'OIDC_PRIVATE_KEY', file_get_contents( '/web-inaccessible/private.key' ) );
</code></pre>
<h3>Define the clients</h3>
<p>Define your clients by adding a filter to <code>oidc_registered_clients</code> in a separate plugin file or <code>functions.php</code> of your theme or in a MU-plugin like:</p>
<pre><code>add_filter( 'oidc_registered_clients', 'my_oidc_clients' );
function my_oidc_clients() {
    return array(
        'client_id_random_string' => array(
            'name' => 'The name of the Client',
            'secret' => 'a secret string',
            'redirect_uri' => 'https://example.com/redirect.uri',
            'grant_types' => array( 'authorization_code' ),
            'scope' => 'openid profile',
        ),
    );
}
</code></pre>
<h3>Exclude URL from caching</h3>
<ul>
<li><code>example.com/wp-json/openid-connect/userinfo</code>: We implement caching exclusion measures for this endpoint by setting <code>Cache-Control: 'no-cache'</code> headers and defining the <code>DONOTCACHEPAGE</code> constant. If you have a unique caching configuration, please ensure that you manually exclude this URL from caching.</li>
</ul>
<h3>Github Repo</h3>
<p>You can report any issues you encounter directly on <a href="https://github.com/Automattic/wp-openid-connect-server" rel="nofollow ugc">Github repo: Automattic/wp-openid-connect-server</a></p>


OpenID Connect Server

Use OpenID Connect to log in to other webservices using your own WordPress.

OAuthRest vs OpenID Connect Server