Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Tenant Specific Permissions in Experience Fragments and Templates

dpeters1
Level 2
Level 2

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?

 

1 Accepted Solution
Arun_Patidar
Correct answer by
Community Advisor
Community Advisor

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)

 

View solution in original post

3 Replies
Arun_Patidar
Correct answer by
Community Advisor
Community Advisor

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)

 

View solution in original post

dpeters1
Level 2
Level 2

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.

dpeters1
Level 2
Level 2
I located the problem. The everyone group granted /content/experience-fragments for jcr:read with no restrictions so it gave read only access to everything. I added rep:glob="" and now my permissions are tenant specific.