Matthias Pfefferle

Will Norris

<p>OpenID is an <a href="http://openid.net/" rel="nofollow ugc">open standard</a> that allows users to authenticate to websites without having to create a new password. This plugin allows users to login to their local WordPress account using an OpenID, as well as enabling commenters to leave authenticated comments with OpenID. The plugin also includes an OpenID provider, enabling users to login to OpenID-enabled sites using their own personal WordPress account. <a href="https://wordpress.org/plugins/xrds-simple/" rel="ugc">XRDS-Simple</a> is required for the OpenID Provider and some features of the OpenID Consumer.</p>
<p>Developer documentation, which includes all of the public methods and hooks for integrating with and extending the plugin, can be found <a href="http://wiki.diso-project.org/wordpress-openid-api" rel="nofollow ugc">here</a>.</p>


OpenID

Allows WordPress to provide and consumer OpenIDs for authentication of users and comments.

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.

OpenID vs OpenID Connect Server