AEM: Anonymous user unable to read /etc/acs-commons/lists/ due to AMS Managed Rule Set blocking .infinity.json requests
This article explains how to resolve access issues for anonymous users attempting to read resources under /etc/acs-commons/lists/ in Adobe Experience Manager when requests are blocked by AMS Managed Rule Set.
Description description
Environment
Adobe Experience Manager (AEM) (all versions)
Issue/Symptoms
Anonymous users are unable to access resources under /etc/acs-commons/lists/ on Production Publish instances. End users report inability to access important event data. Attempts to access URLs such as /etc/acs-commons/lists/dynamic-deck-query-list.infinity.json result in HTTP 403 Forbidden errors, while other URLs (For example: /etc/acs-commons/lists/state-curated.infinity.json) remain accessible.
HTTP 403 Forbidden
The issue is reproducible by navigating to the affected path as an anonymous user. Investigation revealed that requests were being blocked by the AMS Managed Rule Set, except for URLs with explicit allow rules in the AARP Allow URL configuration.
Cause
Requests to .infinity.json endpoints under /etc/acs-commons/lists/ were blocked by the AMS Managed Rule Set, except for URLs with explicit allow rules. Updating the allow list resolved the access issue for anonymous users.
Resolution resolution
Follow the steps below to resolve the issue:
-
Verify Permissions in AEM:
- Log in to the AEM Publish instance as an administrator.
- Navigate to User Administration (
/useradmin). - Search for the anonymous user.
- Ensure that the anonymous user has read access to
/etc/acs-commons/lists/.
-
Check AMS Managed Rule Set:
- Review the AMS Managed Rule Set configuration for the environment.
- Identify if requests to
.infinity.jsonendpoints under/etc/acs-commons/lists/are being blocked.
-
Update AARP Allow URL Configuration:
-
Add a regex pattern to allow all
.infinity.jsonrequests under/etc/acs-commons/lists/:code language-none \/etc\/acs-commons\/lists\/.*\.infinity\.json- Deploy the updated rule set.
-
-
Validate Access:
- After deployment, test access to previously blocked URLs (For example:
/etc/acs-commons/lists/dynamic-deck-query-list.infinity.json) as an anonymous user. - Confirm that HTTP 403 errors are resolved and resources are accessible.
- After deployment, test access to previously blocked URLs (For example: