Adobe Experience Manager Connector Prerequisites

Before you begin the AEM connector deployment, make sure an Adobe Experience Manager Administrator can participate in the deployment process to assign the Adobe Experience Manager specific tasks.

User Accounts and Application Permissions

Required Permission Description
Adobe Experience Manager Account
  • A crawling account must be created in Adobe Experience Manager.
    • Account must have READ access to the following nodes in the repository:
      • Sub-trees containing the content to crawl.
      • Get permissions (rep:policy subnodes) on all ascendants folders of the content to crawl.
      • To all the following nodes:
        /home/users
        /home/groups
        /conf/global/settings/dam/adminui-extension/metadataschema
    • If crawling account is a member of the Administrators group, it automatically has all the permissions specified above.
  • Adobe Granite Token Authentication Handler:
    • Must be enabled
    • Enabled by default
    • Used by Adobe Experience Manager UI as well.

Network and Connectivity

Port Requirement
HTTP/HTTPS The Adobe Experience Manager site must be accessible via HTTP/HTTPS from the server where the connector is deployed

Connector Features and Requirements

Features Supported Additional Information
Adobe Experience Manager
version support
  • Cloud version
  • On-premise versions
  • Authoring instances
    and Publishing instances

Connector is compatible with any Adobe Experience Manager versions that support the Query Builder API.

Connector can be used in the same way either for authoring or publishing instance.

Searchable content types

Digital Assets and Sites.


Content Update Full and Incremental All BA Insight Connectors support both Full and Incremental crawls, unless noted.
Permission Types Yes

All BA Insight Connectors support fetch ACLs from the source system.

To make items public or restricted to a single user/set of users, use Connector Framework.