Tenant Specific Permissions in Experience Fragments and Templates | Community
Skip to main content
D
dpeters1
Level 2
June 10, 2020
Solved

Tenant Specific Permissions in Experience Fragments and Templates

  • June 10, 2020
  • 1 reply
  • 2344 views

I have set up permissions for tenant specific users as follows:

Path = / with restrictions = */tenant

 

This structure has worked to provide tenant specific access in sites and assets, however, this format does not restrict the experience fragments and templates to the same tenant specificity. To troubleshoot, I've attempted to deny jcr:read to path = / with restrictions = */content/experience-fragments/* which does not work either.

I believe the URL for experience fragments including "/aem" is the problem:

Sites --> https://<url>/sites.html/content

Assets --> https://<url>/assets.html/content/dam

Experience Fragments --> https://<url>/aem/experience-fragments.html/content/experience-fragments

 

I'm also seeing the same inability for tenant restrictions in templates, but I need to do some more troubleshooting there since it's under /conf instead of /content.

 

Has anyone else attempted permissions in a multi tenant environment where each tenant only has access to their specific information?

 

    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 arunpatidar

    Hi,

    Yes, we have set up the tenant specific permission for site, assets, templates and experience fragment.

    do not deny permission, just allowed only for the tenant.

     

     

    path: /content/experience-fragments/aem63app permission: allow actions: actions (optional, comma separated)

     

    1 reply

    arunpatidar
    Community Advisor
    arunpatidarCommunity AdvisorAccepted solution
    Community Advisor
    June 10, 2020

    Hi,

    Yes, we have set up the tenant specific permission for site, assets, templates and experience fragment.

    do not deny permission, just allowed only for the tenant.

     

     

    path: /content/experience-fragments/aem63app permission: allow actions: actions (optional, comma separated)

     

    Arun Patidar
      D
      dpeters1Author
      Level 2
      June 11, 2020

      The permissions I have defined are only for allows, however, I attempted the deny to see if I can restrict the permissions effectively at experience fragments which did not work.

       

      I have the following:

      Path: /

      Permission: allow

      Restrictions: rep:glob="*/tenant*

       

      for sites and assets, this permissions grants me specific access to only that one tenant. For experience fragments, I am not seeing the experience fragments that relate specifically to the tenant I've defined.

      Terms & ConditionsAccessibility statement

      Loading footer...