Requesting IMS Client ID and scopes for Adobe Content Advisor integration with a CMS

This article explains how to request and implement the IMS Client ID and scopes required to integrate Adobe Content Advisor with a third-party CMS across multiple environments.

Description description

When integrating Adobe Content Advisor with a third-party CMS, you must provision an official IMS Client ID and a set of IMS scopes for your Adobe IMS Organization. These credentials enable secure authentication and authorization, allowing users to browse and reference assets within the CMS. The same IMS Client ID and scopes are typically used across Development, Staging, and Production environments, but you must provide the details of each environment that will require integration. The integration can’t proceed until the IMS credentials and scopes are provisioned, and the relevant environment domains are registered for authentication.

Environment

  • Adobe Experience Manager (all versions)
  • Third-party CMS

Symptoms

  • Integration setup can’t be completed due to missing IMS credentials.
  • Asset browsing and referencing features are unavailable in the CMS.
  • No explicit error messages, but authentication and authorization don’t succeed.

Cause

IMS Client ID and scope provisioning is required to enable secure integration between Adobe Content Advisor and external CMS platforms. Without these credentials and domain registration, authentication and authorization can’t be established.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Gather the following information for each environment (Development, Staging, Production) where you plan to integrate Content Advisor:

    • Environment name or identifier

    • Domain or URL of the CMS instance

  2. Submit a request through your official Adobe Support channel or Customer Success Manager, specifying:

    • That you require IMS Client ID and scopes for Adobe Content Advisor integration

    • The list of environment domains or URLs that need to be registered for authentication

  3. After receiving the IMS Client ID and scopes from Adobe, add the IMS Client ID to your CMS integration configuration, as required by your CMS or integration pipeline.

  4. Define the list of IMS scopes in your environment configuration according to the information provided by Adobe.

  5. Ensure your CMS application is running on HTTPS and that the registered domains are included in the IMS client configuration.

  6. Follow the official Adobe Content Advisor integration documentation for deployment and configuration steps in AEM User Guide: Content Advisor installation and properties.

  7. Test the integration in each environment to confirm that asset browsing and referencing features are working as expected.

recommendation-more-help
experience-cloud-kcs-help-kbarticles