Scott Joudry

<p>The User Access Hub is a service that allows administrators to manage users, user access, and roles across a network of CMS sites.</p>
<h3>User Access Hub</h3>
<p>The User Access Hub is a service that allows administrators to manage users, user access, and roles across a network of CMS sites and will significantly simplify the administrative tasks associated with managing multiple websites. Some reasons why using such a service can help an administrator effectively manage all their CMS sites:</p>
<ol>
<li>Centralized User Management: The User Access Hub provides a single, centralized dashboard where administrators can manage users across all connected CMS sites. This means that instead of logging into each site separately, they can control user access from one location.</li>
<li>User Account Creation and Deletion: Administrators can grant a user access to one or all CMS sites and revoke/delete user access to one or all CMS sites simultaneously. This is particularly useful when onboarding new users or removing access for users who no longer require it.</li>
<li>Role Management: Administrators can assign CMS site defined roles to users for each CMS site, allowing fine tuned access to each CMS site for each user. Permissions will be assigned to roles that are configured on the CMS site.</li>
<li>Single Sign-On (SSO): The User Access Hub allowing users to log in once and access all connected CMS sites without the need for multiple logins. This enhances user experience and security.</li>
<li>Audit Trail and Logging: The hub maintains detailed logs and an audit trail of user activities and changes made by administrators. This is essential for tracking changes, diagnosing issues, and maintaining security.</li>
<li>Scalability: As the network of Drupal sites grows, the User Access Hub can easily scale to accommodate new CMS sites and users without significantly increasing administrative overhead.</li>
<li>Automation: The User Access Hub service is built on the API first methodology and most of the operations that can be performed in the UI can also be performed using the User Access Hub API.</li>
</ol>
<p><a href="https://www.useraccesshub.com/" rel="nofollow ugc">Create a free account to get started.</a></p>
<h3>Additional features</h3>
<ul>
<li>Drupal CMS support</li>
<li>Core Updates Reporting</li>
<li>Plugin Updates Reporting</li>
<li>Theme Updates Reporting</li>
</ul>
<h3>Requirements</h3>
<ul>
<li>This plugin requires the openssl_verify() PHP function, which is part of the <a href="https://www.php.net/manual/en/book.openssl.php" rel="nofollow ugc">OpenSSL library</a> for PHP.</li>
<li>This plugin requires an account on <a href="https://www.useraccesshub.com/" rel="nofollow ugc">User Access Hub</a>.</li>
</ul>
<h3>Configuration</h3>
<ol>
<li>Enable the plugin. This will create an API key at User Access Hub > Authentication. None of the fields on this form can be edited through the UI. The ‘Enabled the Handshake Endpoint’ checkbox should be checked.</li>
<li>Select the roles that should be handled by the hub’s SSO functionality at User Access Hub > Roles.</li>
<li>Add the site to the <a href="https://www.useraccesshub.com/" rel="nofollow ugc">User Access Hub</a> hub, setting the API key that was generated from step 1.</li>
<li>In the hub, use the ‘Connect’ operation to allow the hub to handshake with the site. Once this is complete, settings on User Access Hub > Authentication will be updated – ‘Private Key’ will be populated, ‘Site ID’ will be populated and the ‘Enabled the Handshake Endpoint’ checkbox will be unchecked.</li>
<li>To enable all User Access Hub functionality, the final step is to check the ‘Enable all of the User Access Hub functionality.’ checkbox on User Access Hub > Settings.</li>
</ol>
<h3>Overriding Configuration</h3>
<p>In many cases, the configuration that exists in the database will need to be overridden. The case of different config values for different environments springs to mind. This can be accomplished by overriding the configuration in a wp-config.php file:</p>
<pre><code>define( 'USERACCESSHUB_ALLOW_LOCAL', true );
define( 'USERACCESSHUB_API_KEY', 'string' );
define( 'USERACCESSHUB_DEFAULT_ROLE', 'role' );
define( 'USERACCESSHUB_ENABLED', true );
define( 'USERACCESSHUB_HANDSHAKE_ENABLED', true );
define( 'USERACCESSHUB_PUBLIC_KEY', 'string' );
define( 'USERACCESSHUB_REDIRECT', '/redirect/url' );
define( 'USERACCESSHUB_ROLES', array( 'role1', 'role2' ) );
define( 'USERACCESSHUB_SITE_ID', 1 );
</code></pre>
<h3>Commands</h3>
<h3>Enable Handshake</h3>
<p>This WP CLI command will enable the handshake endpoint so a site can be reconnected with the Hub.</p>
<pre><code>wp enable-handshake
</code></pre>
<h3>Disable Handshake</h3>
<p>This WP CLI command will disable the handshake endpoint.</p>
<pre><code>wp disable-handshake
</code></pre>
<h3>Regenerate API Key</h3>
<p>This WP CLI command will re-generate the API key used for the handshake.</p>
<pre><code>wp regenerate-api-key
</code></pre>


User Access Hub

The User Access Hub is a service that allows administrators to manage users, user access, and roles across a network of CMS sites.

Zane Matthew

<p>Have you had to make a working project publicly accessible for your client, yet still have to keep<br />
the site “private” to the general public?</p>
<p><strong><a href="http://demo.zanematthew.com/client-access/" rel="nofollow ugc">Demo</a></strong></p>
<p>Normally you’ll quickly hack in an allowed IP list, server-side password (htpasswd), etc. Why hack this in? With Client Access you can take the professional approach. Use a WordPress plugin to allow specific IPs, or those with the universal password the ability to access the work in progress.</p>
<h4>Allow by IP</h4>
<p>Once enabled via the settings tab, you can add a list of IPs to the textarea. These IP addresses are the <em>only</em> IP addresses that are allowed. Additionally you can add a comment per IP to better detail each entry.</p>
<ul>
<li>Provide a list of IPs that are allowed</li>
<li>Comments are allowed for IPs</li>
<li>Display a content message</li>
<li>Display a footer message</li>
<li>All IPs are validated against the latest IP protocols</li>
</ul>
<p>Example:</p>
<pre><code>// Office at 123 Main street
192.168.0.1

// My localhost
127.0.0.1

// Ana
123.456.789
</code></pre>
<h4>Allow by Universal Password</h4>
<p>Once enabled via the settings tab, you can create a universal password that is <em>shared</em> with all users. No user name is required.</p>
<p>Anyone that visits the website while this is enabled will see the default message you’ve added. The site will only be accessible to users that you have shared out the password with.</p>
<ul>
<li>Provide a universal password</li>
<li>Set an expire time</li>
<li>Display a content message</li>
<li>Display a footer message</li>
</ul>
<h4>Allow By Role</h4>
<p>Allow by role of choice.</p>
<ul>
<li>Choose any registered role</li>
<li>Display a content message</li>
<li>Display a footer message</li>
</ul>
<h4>Translations</h4>
<ul>
<li><a href="http://www.echodesplugins.li-an.fr/" rel="nofollow ugc">French</a></li>
<li><a href="http://dianakolnik.com/" rel="nofollow ugc">Spanish</a></li>
</ul>


Client Access

Let your client see their work in progress.

User Access Hub vs Client Access