Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

[AEM Gems Webinar] Accelerating Experience Manager as a Cloud Service development with Rapid Development Environments

Dispatcher not respecting CUG restriction on parent node


Level 1

I've been investigating the below dispatcher issue. Can you please provide pointers on the below.

I have a cq:Page titled 'index' and under this page there is 'xyz.html'. This is only visible to group "xyz1" and not visible to group "xyz2" configured on the publisher. Initially when cache is empty a user in group xyz2 will see a 404 - Not Found error for the following requests made in the browser: 1), 2)

When a user from group xyz1 requests URLS 1) and 2) above, the docs are cached separately in docroot and are seen in the cache as the following: 1) ../docroot/content/index.html and 2) ../docroot/content/index/xyz.html as expected.

When user from group xyz2 requests the cached documents they are able to access which is NOT expected. However the user still gets a 404 - Not Found error when they access the 2nd URL: which is expected. It appears that CUG entitlement check is NOT being respected on the cached parent node (.../index.html) but it is being applied on the child node (.../index/xyz.html).

A few things about my current setup: 1) allowAuthorized is '1', 2) dispatcher is configured to cache *.html, 3) Permission Sensitive Caching IS ENABLED (implemented using

I read this dispatcher issue but it appears to be different from what we are experiencing:

2 Replies


Level 1

CUG is applied on the parent node e.g on the path: /content/index