Access issue for etc in AEM 6.4 | Community
Skip to main content
Parusharam
Level 2
March 15, 2019
Solved

Access issue for etc in AEM 6.4

  • March 15, 2019
  • 5 replies
  • 3227 views

Hi, Is it mandatory to give access to everyone group to the /etc/designs explicitly in AEM 6.4? We have compressed clientLibs under etc/designs and they are not loading in publishers without giving access to everyone group in /etc.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Gaurav-Behl

That is called as "anonymous"/unauthenticated access to content. There is a user with the name "anonymous" in publish server to whom you need to assign appropriate read permissions either on the user itself or via its associated group which is 'everyone' in this case.

Anonymous access is required for /content & /etc paths for the app to work. Make sure to limit down the read access to specific paths.

5 replies

Gaurav-Behl
Level 10
March 15, 2019

With what user did you try to access the content? That user should have appropriate read permissions (assigned to the user directly or via its group) to access the content.

Please provide more information on what did you access, what permissions did you provide in case you can't figure it out.

Parusharam
Level 2
March 15, 2019

I am trying to access the page in publisher environment without login into publisher.i.e everyone group.

Gaurav-Behl
Gaurav-BehlAccepted solution
Level 10
March 15, 2019

That is called as "anonymous"/unauthenticated access to content. There is a user with the name "anonymous" in publish server to whom you need to assign appropriate read permissions either on the user itself or via its associated group which is 'everyone' in this case.

Anonymous access is required for /content & /etc paths for the app to work. Make sure to limit down the read access to specific paths.

Parusharam
Level 2
March 15, 2019

Is it same with 6.2..? Same pages are loading without giving access in 6.2

Gaurav-Behl
Level 10
March 15, 2019

It is the same behavior for all AEM versions.

If it works fine w/o providing read access then you may check "sling authentication service" configurations under "/system/console/configMgr" to validate that you have "-/etc/<something>" 

minus sign is to allow anonymous access

plus sign is to enforce to authentication