Connecting to AEM repository with Davex bundle disabled
This article explains how to connect to the AEM JCR repository from an external source when the Davex bundle is disabled due to security concerns. By following the outlined alternative methods, you can ensure secure repository access while maintaining compliance with AEM’s security standards.
Description description
Environment
Adobe Experience Manager (AEM) version 6.5
Issue/Symptoms
When attempting to connect to the AEM repository using the following code:
Repository repository = JcrUtils.getRepository("http://localhost:4503/crx/server");
an error occurs if the Davex bundle (org.apache.sling.jcr.davex) is disabled, showing: Authentication required to access repository descriptors
This may also trigger javax.jcr.ItemNotFoundException and related stack trace errors, blocking repository access.
Resolution resolution
To resolve this issue, consider the following alternatives for connecting to the AEM repository:
-
SlingPostServlet
- Write custom scripts to handle POST requests for creating or modifying resources within the repository.
- Suitable for programmatic content updates.
-
PackageManager API
- Create a content package containing the desired nodes and install it using the PackageManager API.
- Ideal for bulk content updates or migration tasks.
-
Custom Endpoint (API)
- Develop a custom servlet or similar component that expose specific AEM functionalities as an API endpoint accessible to external clients.
- Useful for custom integrations requiring specific operations.
These approaches allow secure repository access without relying on the Davex bundle. For assistance with implementation, consider contacting your Adobe Partner or the Adobe Professional Services team.