When AEM Communities is configured to use ASRP as its common store, user generated content (UGC) is accessible from all author and publish instances without the need for synchronization nor replication.
An additional license is required for the use of ASRP.
To configure your AEM Communities site to use ASRP for UGC, contact your account representative for:
The consumer and secret keys are shared across all report suites for a company. There is one report suite per tenant.
The Storage Configuration console allows for the selection of the default storage configuration, which identifies which implementation of SRP to use.
On AEM Author instance:
The following information comes from the provisioning process:
Prepare the publish instances:
After submitting the configuration, test the connection:
Select Test Config.
For each author and publish instance, test the connection to the data center from the Storage Configuration console.
Ensure that the site URLs for profile data are routable from the Data Center by externalizing links.
The Consumer Key and Secret Key are encrypted. In order for the keys to be encrypted/decrypted properly, the primary Granite Crypto key must be the same on all AEM instances.
Follow the instructions at Replicate the Crypto Key.
For correct profile and profile image links, be sure to properly Configure the Link Externalizer.
Be sure to set the domains to be URLs that are routable from the Data Center URL (ASRP endpoint).
In order for authentication with the ASRP endpoint to succeed, the machines running your hosted AEM Communities must be time synchronized, such as with the Network Time Protocol (NTP).
ASRP must be identified as the common store on all author and publish instances.
To make the identical configuration available in the publish environment:
On AEM Author instance:
If you enable ASRP on a published community site, any UGC already stored in JCR is no longer visible, as there is no synchronization of data between on-premise storage and cloud storage.
AEM Communities Extension was previously introduced in AEM 6.0 social communities as a cloud service. As of AEM 6.1 Communities, no cloud configuration is necessary, simply select ASRP from the storage configuration console.
Due to the new storage structure, it is necessary to follow the upgrade instructions when upgrading from social communities to Communities.
For information regarding users, user profiles and user groups, often entered in the publish environment, visit
If upgrading from an existing AEM 6.0 social community site, be sure to follow the upgrade instructions, else UGC appears to be lost.
If receiving authentication errors against the Data Center URL, and the AEM error.log contains messages about stale timestamps, then verify that time synchronization is happening.
Use a tool such as the Network Time Protocol (NTP) to time synchronize all AEM author and publish servers.
The Adobe cloud storage infrastructure uses eventual consistency to achieve its scaling and performance goals. For this reason, new content is not instantly available and it takes several seconds for it to appear in search results.
While the interval affecting eventual consistency is monitored, contact your account representative if it takes longer than a few seconds for new content to appear in searches.
Make sure that the ASRP has been configured to be the default provider by checking the configuration of the storage option. By default, the storage resource provider is JSRP, not ASRP.
On all author and publish AEM instances, revisit the Storage Configuration console, or check the AEM repository.
In JCR, if /conf/global/settings/communities: