Adobe Experience Manager Sites & More

varshsr · 10/15/15

Hi All,

Using AEM as an intranet portal - following are my thoughts on enabling role based menu navigation for end user - some links hidden for certain roles / some links disabled

option 1 - client context would be my recommendation any view on this or any other better?

1) use the client context with custom role trait and deliver teaser (pre authored with multiple menus for the different roles) - gives the content author to realize the experience and extensible for additional roles

2) use JavaScript based function checks along with css hide/show - needs a code change every time

3) try it using server side - like role based checks on jsp/jstl. but if these pages are cached then big issue

4) create menu links as content fragments and tag with separate role based etc/tags and use a servlet json to fetch the links (on ajax) and do a client side layout

can we still cache the pages with dynamic menu ?

Jörg_Hoh · 10/15/15

Hi,

The question is: Does the header need to show "personalized" information or only "targeted" information? Personalized means, that this kind of information must be reachable by other unauthorized roles. Targeted means, that it doesn't matter if other people, which normally don't see this information, get access to it.

In the second case you can use the simple selector-based approach as described by Sham HC. In the first case you need to combine it with permission sensitive caching (or just have it dynamically created on AEM side, if you have too many combinations of groups, which will cause problems when you create that many files...)

kind regards,
Jörg

View solution in original post

Jörg_Hoh · 10/15/15

Hi,

The question is: Does the header need to show "personalized" information or only "targeted" information? Personalized means, that this kind of information must be reachable by other unauthorized roles. Targeted means, that it doesn't matter if other people, which normally don't see this information, get access to it.

In the second case you can use the simple selector-based approach as described by Sham HC. In the first case you need to combine it with permission sensitive caching (or just have it dynamically created on AEM side, if you have too many combinations of groups, which will cause problems when you create that many files...)

kind regards,
Jörg

Sham_HC · 10/15/15

You are making things too complicated to use client context ....
Designing nice structure & assigning out of the box acl with custom simple navigation component can solve this issue.
use selector for navigation component. So that selector equals role & there by you can cache it.

varshsr · 10/15/15

yes these 200k users will be mapped to multiple roles in identity and would like to use that information via client context custom data store for authorization can white list the URLs for roles with regex patterns as custom config acl like we white list selectors or use saml to authorize the URL and maintain content structure based to roles aligned to a common blueprint Or Would it be better to have 200k users maintained and mapped to groups in crx and use cug? But as I have stated earlier managing these end users /group in crx could be cumbersome with arm ui and even if use psc for caching all the pages would required to be authorized as this is a menu component which is available on all pages

varshsr · 10/15/15

Hi,

Thanks for the info, I did not specify this earlier , In my case i do not want to store end user profile in AEM so after external authentication(SAML) want to drive restricted menus on headers having a teaser and different menu campaigns attached created by authors .This gives authors to preview the different menus based on client context UI as custom data store would have loaded the traits to support 2,00,000 users(different user roles).

But if go with ACL based approach I am thinking of user / groups/acl management within AEM UI being more cumbersome to support 2,00,000 users

Also the links in menu can also be external links so it might not fit a direct navigation component within a content structure.

And for internal links when content grows ACL check for content will be a challenges at it will be applied for each resource request practically and author have to modify ACL if any updates to menu listing.

Now please tell me if client context works well or i have to go by ACL with users maintained in AEM.

Also it will be on AEM TarMK with multiple publish instance to drive the user load.

Also these menus will be part all the pages and is it possible to cache the page which has a client context target - I feel yes as it is going to an Ajax call to load the role based menus - Please let me know other wise

Overall this menu should be visible for the user role and has to be support without any future code change as well.

as in below and the teasers to have different menu expereinces

https://docs.adobe.com/content/docs/en/aem/6-0/develop/personalization/client-context/_jcr_content/p...

varshsr · 10/15/15