logo
logo

Setup

The Sitecore Connect for Content Hub connector requires that you configure Sitecore Content Hub as well as your Sitecore instances.

This configuration applies to Sitecore Content Hub 3.3.0 and later.

Note

If you are consuming public links and have whitelisted any of the stylelabs.cloud domains in the CORS configuration, you need to whitelist the sitecorecontenthub.cloud domain as well.

CORS configuration

You must configure CORS for Content Hub to allow incoming traffic from the Sitecore instance.

To configure CORS:

  1. In Content Hub, on the menu bar, click Manage .

  2. On the Manage page, click Settings.

  3. On the Settings page, in the Search box, type CORSConfiguration and press Enter.

  4. In the PortalConfiguration list, select CORSConfiguration.

  5. Add the Sitecore instance URL to the list of URLs (for example, https://www.sitecore.instance.com).

  6. Click Save.

Portal configuration

You need to configure the redirection setting within PortalConfiguration to allow the Sitecore instance to access and display the contents of the Sitecore DAM.

  1. In Content Hub, on the menu bar, click Manage .

  2. On the Manage page, click Settings.

  3. On the Settings page, in the Search box, type Authentication and press Enter.

  4. In the PortalConfiguration list, select Authentication.

  5. In the right pane, under ExternalAuthenticationProviders change the authentication_mode for all SSO providers to Passive:

    "sitecore": [
          {
            "authentication_mode": "Passive",
            "client_id": "<ClientId>",
            "client_secret": "<ClientSecret>",
            "email_claim_type": "<ClaimTypeOverride>",
            "external_user_creation_url": "https://www.registerme.com",
            "identity_server_url": "<Url>",
            "is_enabled": true,
            "messages": {
              "signIn": "translationKey",
              "signInDescription": "translationKey",
              "signInTitle": "translationKey"
         },
           "provider_name": "Sitecore,",
           "username_claim_type": "<ClaimTypeOverride>"
         }
       ]
Note

If you do not have SSO configured, basic authentication is used and the authentication_mode is set to Passive by default.

Warning

From Content Hub 3.4.0 onwards, the translation keys provided in the messages configuration for the login page need to be provided without the T_ prefix. For example, "signIn": "T_translationKey" should be "signIn": "translationKey".

Can we improve this article ? Provide feedback