CUG Dispacher Configuration | Community
Skip to main content
N
nsvsrk
Level 8
October 16, 2015
Solved

CUG Dispacher Configuration

  • October 16, 2015
  • 2 replies
  • 1321 views

Hi,

Let us say, we created a new group; for example, cug_access for the purpose of demonstrating Closed User Group concept.

Also, we assigned it to a page called restrict.html using the Page Properties ==> Advanced ==> Closed User Group using the CQ Interface.

Please suggest how to configure Dispatcher, so that access of restrict.html is given to only members of  group cug_access.

Setting /allowAuthorized  to "0" in the /cache section alone would do?

Or we have to set values for /sessionmanagement and its sub-parameters, like /directory?

Please refer to

Appreciate your help.

Thanks,

Rama.

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 joerghoh

Hi,

CUG is purely implemented on publish. You need to make sure, that the resulting pages are not cached, so /allowAuthorized "0" is correct. If you want cache such content nevertheless, you have to use the permission sensitive caching (PSC) feature of the dispatcher.

kind regards,
Jörg

2 replies

Sham_HC
Sham_HC
Level 10
October 16, 2015

You need to apply sessionmanagement also & required changes are explained at http://docs.adobe.com/docs/en/aem/6-0/administer/security/cug.html

Additionally If you are having more than one publish instance then need to configure stickyConnectionsFor Or enable crypto support. 

You might think about https://docs.adobe.com/docs/en/dispatcher/permissions-cache.html

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
October 16, 2015

Hi,

CUG is purely implemented on publish. You need to make sure, that the resulting pages are not cached, so /allowAuthorized "0" is correct. If you want cache such content nevertheless, you have to use the permission sensitive caching (PSC) feature of the dispatcher.

kind regards,
Jörg

Terms & ConditionsAccessibility statement

Loading footer...