Friday 6 May 2016

Using the Sling API to Query AEM Resources that belong to a Closed User Group

You can create an Adobe Experience Manager (AEM) application that queries AEM resources located in the AEM Java Content Repository (JCR) and part of a Closed User Group. To query AEM resources, you can use the Sling API from within an OSGi bundle to retrieve a resource from within the AEM JCR. To use the Sling API from within an OSGi component, you inject an org.apache.sling.api.resource.ResourceResolverFactory instance into the service. See Interface ResourceResolverFactory.

To use the Sling API to query AEM resources that belong to a CUG, you have to use an AEM System user that meet these requirements:


  • belongs to the CUG
  • has read permissions to the AEM resources

For example, consider the following AEM page resouces that are children pages to /content/geometrixx/en/toolbar/contacts.


To read this development article, click https://helpx.adobe.com/experience-manager/using/querying-experience-manager-sling-cug.html. 

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner




I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


Twitter: Follow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel. 





at