Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

AEM 6.4 RETRICT THE PAGES access.

Avatar

Level 2

Hi team, I am very keen to get the answer for the below query.  1: how to restrict few pages access for our website.     2: how to lock any component or content if two author simultaneously editing the content 3: how to retrict my clientlibrary only for specific component not for page. 4: how to restrict app folder access in polish instance if app is restricted then how public instance load client libs which are created in apps .                  Team, it a Great help for me if anyone of you can answer my 4 equities from a boy. I would really appreciate please

1 Accepted Solution

Avatar

Correct answer by
Employee

Hi @ashutot1,

Please find responses to your queries inline:

 

~ How to restrict few pages access for our website?

>> You can always restrict pages/nodes from http://localhost:6530/useradmin and define the permissions (read, create, modify, delete etc) to be granted or denied for users/group. By this way, you can restrict the page access from AEM perspective. Other way is to restrict them at dispatcher level by creating some filter rules in your dispatcher.any file. See https://docs.adobe.com/content/help/en/experience-manager-dispatcher/using/configuring/dispatcher-co....

 

~ How to lock any component or content if two author simultaneously editing the content?

>> You can leverage page lock functionality for this. https://docs.adobe.com/content/help/en/experience-manager-65/authoring/authoring/editing-content.htm....

 

 How to restrict my clientlibrary only for specific component not for page?

>> You can move your clientLibs specific to component level.

example:  /apps/myproject/clientLibs or /apps/myproject2/clientLibs2 or /apps/myproject3/clientLibs3

 

~ How to restrict app folder access in publish instance if app is restricted then how public instance load client libs which are created in apps?

>> Clientlibs under /apps should have the "allowProxy" property and will be invoked via a proxy servlet. It is recommended to locate client libraries under /apps and expose them via /etc.clientlibs by leveraging the allowProxy property. So if the file is like /apps/projects/clientlibs/base/resources/icon.png then it will be accessed via /etc.clientlibs/projects/clientlibs/base/resources/icon.png

 

Along with this you will need to add the below rules in dispatcher.

  1. under filter section allow the below path:
    /0002 { /type "allow" /url "/etc.clientlibs/*" }
  2. under rules section allow the below paths:
    /0001 { /glob "/etc.clientlibs/*.css" /type "allow" }
    /0002 { /glob "/etc.clientlibs/*.js" /type "allow" }

Please refer the below link for more details:

https://docs.adobe.com/content/help/en/experience-manager-65/developing/introduction/clientlibs.html...

 

Thanks!!

 

 

View solution in original post

1 Reply

Avatar

Correct answer by
Employee

Hi @ashutot1,

Please find responses to your queries inline:

 

~ How to restrict few pages access for our website?

>> You can always restrict pages/nodes from http://localhost:6530/useradmin and define the permissions (read, create, modify, delete etc) to be granted or denied for users/group. By this way, you can restrict the page access from AEM perspective. Other way is to restrict them at dispatcher level by creating some filter rules in your dispatcher.any file. See https://docs.adobe.com/content/help/en/experience-manager-dispatcher/using/configuring/dispatcher-co....

 

~ How to lock any component or content if two author simultaneously editing the content?

>> You can leverage page lock functionality for this. https://docs.adobe.com/content/help/en/experience-manager-65/authoring/authoring/editing-content.htm....

 

 How to restrict my clientlibrary only for specific component not for page?

>> You can move your clientLibs specific to component level.

example:  /apps/myproject/clientLibs or /apps/myproject2/clientLibs2 or /apps/myproject3/clientLibs3

 

~ How to restrict app folder access in publish instance if app is restricted then how public instance load client libs which are created in apps?

>> Clientlibs under /apps should have the "allowProxy" property and will be invoked via a proxy servlet. It is recommended to locate client libraries under /apps and expose them via /etc.clientlibs by leveraging the allowProxy property. So if the file is like /apps/projects/clientlibs/base/resources/icon.png then it will be accessed via /etc.clientlibs/projects/clientlibs/base/resources/icon.png

 

Along with this you will need to add the below rules in dispatcher.

  1. under filter section allow the below path:
    /0002 { /type "allow" /url "/etc.clientlibs/*" }
  2. under rules section allow the below paths:
    /0001 { /glob "/etc.clientlibs/*.css" /type "allow" }
    /0002 { /glob "/etc.clientlibs/*.js" /type "allow" }

Please refer the below link for more details:

https://docs.adobe.com/content/help/en/experience-manager-65/developing/introduction/clientlibs.html...

 

Thanks!!