closed user group

[varshsr]

We are planning to setup a portal with 10+ CUG for authenticated users via LDAP. These CUG's to have secure access to group only pages.

Also we want these pages to be cached and checking on permission sensitive caching.

1) for permission sensitive caching is it ok to support 10+ CUG's ?

2) what is the use of /sessionmanagement  in dispatcher.any , what is the effect of more that 1 CUG to this configuration

3) Need comparison between /sessionmanagement vs PSC  (/auth_checker) ,  what is the effect of more that 1 CUG to this configuration

[varshsr]

any help / ideas on these topics ?

[kautuk_sahni]

hi sri003

I would ask internal engineering team, if they have some input for the same.

Please wait till next response. 

Thanks and Regards

Kautuk Saahni 

[varshsr]

Thanks ,Please share if any details 

[Jörg_Hoh · Accepted solution]

Hi,

to your questions:

1) yes, there is no technical limit on the number of supported CUGs.

2) /sessionmanagement has no effect on the CUG and/or PSC handling (at least I haven't dealt with it in the cases where I used PSC and CUGs)

3) From what I know, PSC does not rely at all on the sessionmanagement as offered by the dispatcher. You can combine both, that's fine. But PSC works when you identified users, and you need to check on the dispatcher, if the dispatcher is allowed to deliver a secured file to the user. PSC is the "call AEM and ask if this authenticated user is allowed to access the file" mechanism, for the authentication process you can choose whatever you want.

Jörg

[varshsr]

Thank Jörg,

Few interesting questions,based on this link http://dev.day.com/docs/en/cq/current/howto/create_apply_cug.html

I see on one side it speaks about CUG needs /sessionmanagement and these pages cannot be cached (/allowAuthorized 0)

on other side CUG pages can be cached /auth_checker (/allowAuthorized 1)

When see form an AEM performance perspective and dispatcher should cache as much as possible 

is /sessionmanagement obsolete or there any relevant use cases for the same ? or only  /auth_checker is  valid in the context of CUG