ÃÛ¶¹ÊÓƵ

Permission errors for campaign-remote user when linking AEM to Campaign Classic

This article discusses how to resolve permission errors for a campaign-remote user when linking ÃÛ¶¹ÊÓƵ Experience Manager (AEM) to ÃÛ¶¹ÊÓƵ Campaign Classic (ACC). The resolution involves ensuring that you have replication permissions for all required paths in your integration setup.

Description description

Environment

  • ÃÛ¶¹ÊÓƵ Experience Manager (AEM) Managed Services Support, version: 6.5 Relevant Component: AEM Sites
  • ÃÛ¶¹ÊÓƵ Campaign Classic (ACC)

Issue/Symptoms

When attempting to connect AEM with an instance of ACC, pages authored in AEM appear in the Campaign interface. However, clicking these pages results in errors due to permission issues. Error logs typically indicate that the current session lacks authorization to replicate paths within the content (/content/ or /content/experience-fragments) and configuration (/conf) directories. This often happens when experience fragments used in email templates are stored under the /conf path, leading to errors like:

Current session is not authorized to replicate /content/experience-fragments/\[ path]
Current session is not authorized to replicate /conf/commons/email/settings/wcm/templates/\[ path]

These errors suggest a permission issue with replication rights for out-of-the-box users like  campaign-remote.

Resolution resolution

To resolve this issue without altering default user permissions directly, follow these steps:

  1. Ensure that the campaign-remote user has replication permissions for all required paths involved in your integration setup.

    Additional paths such as /content/experience-fragments or configurations under /conf/commons/email/settings/wcm/templates may also require replication permissions.
  2. Instead of modifying existing out-of-the-box user permissions, which may be overwritten during updates or service pack installations, create a new user group.
  3. Grant this new group the required replication permissions across all relevant content and configuration paths.
  4. Add the campaign-remote user to this newly created group so it inherits these necessary permissions.

These steps can help ensure that your integration remains stable through upgrades while maintaining proper access controls needed for successful synchronization between AEM and ACC.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f