WordPress plugin

The DocID^® WordPress plugin is the quickest integration path for a standard WordPress website. It implements the OAuth redirect and lets administrators protect supported WordPress content.

Open the DocID^® plugin on WordPress.org

Prerequisites

• A WordPress website on HTTPS
• Permission to install and configure plugins
• A DocID^® asset and OAuth client for the target environment
• The client ID and client secret supplied for that asset

Configure the plugin

1. Install and activate the DocID^® plugin from the official WordPress.org listing above.
2. Open Settings → DocID^®.
3. Enter the client ID and client secret for the correct environment.
4. Copy the callback URL shown by the plugin and register it in DocID^®.
5. Select the content that should require a DocID^® login.
6. Save the settings and test the flow in a private browser window.

Register the callback exactly as shown for the website. A different scheme, hostname, path, query, or trailing slash causes the authorization request to fail.

Requested customer data

The openid and professional scopes are always enabled. They provide sub, profession_id, discipline_id, and profession_verified for authentication, access checks, and stable account linking.

The optional profile, email, and phone scopes are disabled by default. Enable only the customer data the website actually needs. DocID® transfers these optional data only after the user authorizes the transfer.

Test before launch

• Open protected and public content while signed out.
• Complete login with an eligible test account.
• Continue without authorizing optional customer data and verify that sign-in and the return redirect complete with the baseline claims.
• Sign out and verify protected content is no longer accessible.
• Check pages, posts, and protected media links relevant to your setup.

For plugin-specific problems, see Troubleshooting.

Troubleshooting

If sign-in does not return the visitor to the requested page, update to the latest plugin version, clear active website caches, and repeat the complete flow in a private browser window.

Configure cache plugins, reverse proxies, and CDNs to treat DocID® authentication requests and protected content as dynamic and to honor the plugin's cache-control responses. Follow the cache provider's guidance for authentication integrations.

Verify that the registered callback URL exactly matches the URL shown by the plugin. If the problem persists, provide the WordPress and plugin versions, the affected URL, and the approximate test time to support.