After installing Content Hub client modules, configure the module user permissions to administer and use the service, and then use the Drupal admin interface to configure them to connect your website to the Content Hub repository.

Content Hub modules must connect to the Content Hub service to publish from and subscribe to content.

1. To obtain the information that you need to be enter in the Personalization Credential section:

   1. Open a new browser tab.

   2. Sign in to Personalization using an account with administrative permissions.

   3. Click the Configure tab.

   4. Click the Customer Data link.

   5. If you are a Personalization - Standard user, click Content Hub Admin User.

   6. Click the customer name with the Content Hub settings that you want to inspect.

   7. In the Content Hub Module section, note the following values:

      • Acquia Content Hub Hostname

      • API Key

      • Secret Key

      • Client Name

      Notes

      • Personalization Standard subscribers must contact Acquia Support to retrieve their API Key and Secret Key.

      • If you uninstall and reinstall Content Hub at any point, you cannot reuse the previously used client name. However, you can use a similar name by appending the previously used name with a unique number. For example, if the previously used name is PERSONALIZATIONSITE, you can use PERSONALIZATIONSITE2.

      • The ach-connect Drush command requires the same inputs, allowing you to register a client using Drush instead of in the form.

2. In the Drupal administration menu, click Configuration > Web services and then click the Acquia Content Hub link (http://[site_URL]/admin/config/services/acquia-contenthub).

3. Update the Content Hub configuration values based on the matching values from the Personalization interface.

4. Click Save Configuration.

Repeat the steps for each new website or environment to register new clients with Content Hub.

Store all the settings found in the configuration acquia_contenthub.admin_settings as a configuration split, or set them in the settings.php file. See the example files for suggestions.

Download and configure a per-environment settings file to ensure the data from your production environment isn’t corrupted by data from non-production environments.

To check this using drush, run the following command on each site in each environment:

drush cget acquia_contenthub.admin_settings --include-overridden

Your website is now connected to the Content Hub content repository, and can begin to share content with your other connected websites.

For examples using more than one website for publication and syndication, see Registering multiple Content Hub 1.x clients.

drush upc drupal
composer require drupal/acquia_contenthub:~1.0
drush cr