Resolve CORS and access issues for Dynamic Media OpenAPI Content Advisor integration
This article explains how to address CORS errors and access rights issues that occur when integrating the Content Advisor feature of Dynamic Media OpenAPI with non-Adobe applications.
Description description
When integrating the Content Advisor feature of Dynamic Media OpenAPI with a non-Adobe application, such as a custom web app or local development environment, you see CORS-related errors and access denials. These issues often arise if the IMS client configuration doesn’t include your application’s domain in the allowed redirect URIs and CORS origins, or if the user or service principal lacks the necessary permissions to access assets in the Dynamic Media environment.
Environment
- Adobe Experience Manager Dynamic Media OpenAPI (all versions)
- Integration with non-Adobe applications (For example: custom web apps, local development servers)
Symptoms
- CORS errors in the browser console when accessing the Content Advisor interface from a non-Adobe origin
- Access is blocked for the IMS client when requests originate from your development or test domain.
- Example error: Access to fetch at ‘https://…/contentadvisor/…’ from origin 'http://
Cause
These errors occur because the IMS client isn’t authorized for the requested origins and redirect URIs. Additionally, the user or service principal may not have sufficient permissions to search for assets in the Dynamic Media with OpenAPI environment.
Resolution resolution
Follow the steps below to resolve the issue:
-
Verify IMS client permissions:
-
Ensure that the user or service principal used to connect to Dynamic Media with OpenAPI is authorized to search for assets in your Dynamic Media environment.
-
Confirm that the necessary permissions are assigned to the IMS client in the Adobe Developer Console.
-
-
Request whitelisting of development or test domains:
-
Prepare a list of the domains and URLs (such as your development or test domain) that need to be whitelisted.
-
Contact your Adobe administrator or support team with access to the IMS client configuration to request that these domains and URLs be added to the allowed lists (Allowed Redirect URIs, Allowed Origins for CORS, and Allowed PostMessage Origins).
-
-
Test the integration:
-
After the required domains and URLs are whitelisted, retry the integration from your non-Adobe application.
-
Confirm that CORS errors are resolved and that the Content Advisor feature is accessible.
-
-
If issues persist, verify that the IMS client and user or service principal have the correct permissions to access the required assets.