Skip to main content
Gradial uses the Content Hub REST API to manage assets, Content Items, and Campaigns. For a new connection, use a Content Hub OAuth client with Client Credentials authentication. The username and password method remains available for existing connections.

Connect with OAuth Client Credentials

Create one OAuth client for Gradial and associate it with one dedicated Content Hub service user. Assign that user the groups and policies needed for your Gradial workflows. This example shows a completed Content Hub OAuth Client form. The displayed values are examples: Content Hub OAuth Client form showing the Client ID, Client Secret, Redirect Url, Client Type, Users, and Is Enabled fields

Generate a Client Secret

Content Hub requires a printable ASCII client secret. A strong example is 32 cryptographically random bytes encoded as 64 hexadecimal characters. On macOS or Linux, use OpenSSL if it is installed:
On Windows, use PowerShell without installing OpenSSL:
Both commands produce a 64-character hexadecimal string. You can also use an approved secret generator that uses cryptographically secure randomness. Save the Client Secret securely for the Gradial connection form. To create the connection:
  1. In Content Hub, create the dedicated service user and assign its required groups and policies.
  2. Go to Manage → OAuth clients and add an OAuth client.
  3. Enter a descriptive Name and a unique Client ID.
  4. Generate a unique Client Secret with one of the methods above and enter it in Content Hub.
  5. Enter an HTTPS placeholder URL in the required Redirect Url field. Sitecore requires a value, but the Client Credentials grant does not use it. The URL in the screenshot is an example, not a Gradial callback endpoint. Leave Redirect URLs empty unless your Content Hub instance requires a value there too.
  6. Set Client Type to Client Credentials.
  7. Add the dedicated service user in Users. Use only one user. If you add several, Content Hub authenticates as the first user only.
  8. Select Is Enabled and save the OAuth client.
  9. In Gradial, go to Settings → Integrations and add Sitecore Content Hub. Enter the Content Hub base URL, Client ID, and Client Secret. Leave OAuth Client Credentials selected, then select Validate Connection and Create Connection.
Validation checks that Gradial can get an access token and read entity definitions. It does not test write permissions. Give the service user the Content Hub policies needed for later create, update, and delete operations. For more about the OAuth client fields, see Sitecore’s authentication guide.

Connect with a username and password (legacy)

Use this method only when the Content Hub user has a local password. An identity provider sign-in does not supply one. In Gradial, go to Settings → Integrations and add Sitecore Content Hub. Select Username and Password (legacy), then enter the Content Hub URL, username, and password. Validate Connection checks campaign create, read, and delete access before Create Connection becomes available. Existing password connections continue to work.