Content Hub follows the module conventions contributed by the Drupal community and stores various module settings in Drupal config entities. These conventions include the following credentials and unique identifiers stored under acquia_contenthub.admin_settings.*:

Best practices for managing credentials

• Restrict the Content Hub accounts to one Cloud Platform environment

  Your production Content Hub account must contain only clients and entities from production Drupal sites. Content Hub does not enforce or restrict this, but Acquia recommends it as a best practice to avoid confusion and challenges when troubleshooting syndication.

• Store the Content Hub API key and secret key in a settings.php include file instead of the database

  These credentials are used to authenticate to a specific Content Hub account. If the credentials are stored in the database, and you copy the production database to a lower environment such as staging, the staging environment authenticates to Content Hub as if it is the production site. This can cause content changes made in staging to be syndicated to live production sites. For more information, see Storing sensitive information outside of your codebase.

• Export the client UUID, webhook UUID, and shared secret cautiously

  These values can be changed by the Content Hub service instead of the Drupal site. For example, Drush can be used to regenerate the shared secret. If the Drupal site becomes out of sync with the values stored in the service, syndication fails. Consider using the config_split contrib module for better control over exporting module configuration.

• Scrub the client UUID, webhook UUID, and shared secret stored in the database when staging down databases

  Acquia recommends you to run scrub scripts if a database is copied across environments so that the scripts remove the site-specific configuration. If you use Site Factory, see Scrubbing sensitive data from staged sites for informtion about scrub scripts.

Validate configuration

After applying the best practices, you can validate that your configuration is set up correctly on each connected site.

drush cget acquia_contenthub.admin_settings --include-overridden

$ drush ach-chs
Content Hub Credentials being used and if there have been any overrides:
+----------------------------------------+------------+------------------+------------+--------------------------------------+---------------------+-------------------+--------+
| Hostname                               | Name       | API Key          | Secret Key | Origin UUID                          | Shared Secret       | Settings Provider | In Use |
+----------------------------------------+------------+------------------+------------+--------------------------------------+---------------------+-------------------+--------+
| https://example.content-hub.acquia.com | EXAMPLE123 | ExampleAPIKey123 | ********   | xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx | sharedsecretexample | core_config       | Yes    |
+----------------------------------------+------------+------------------+------------+--------------------------------------+---------------------+-------------------+--------+

Managing Content Hub credentials

drush cget acquia_contenthub.admin_settings --include-overridden

$ drush ach-chs
Content Hub Credentials being used and if there have been any overrides:
+----------------------------------------+------------+------------------+------------+--------------------------------------+---------------------+-------------------+--------+
| Hostname                               | Name       | API Key          | Secret Key | Origin UUID                          | Shared Secret       | Settings Provider | In Use |
+----------------------------------------+------------+------------------+------------+--------------------------------------+---------------------+-------------------+--------+
| https://example.content-hub.acquia.com | EXAMPLE123 | ExampleAPIKey123 | ********   | xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx | sharedsecretexample | core_config       | Yes    |
+----------------------------------------+------------+------------------+------------+--------------------------------------+---------------------+-------------------+--------+

(Optional) You can use drush acquia:contenthub:remote-settings or drush ach-rs to verify the Drupal site’s connectivity to the Content Hub service:

(Optional) You can use drush acquia:contenthub:remote-settings or drush ach-rs to verify the Drupal site’s connectivity to the Content Hub service: