[
https://issues.apache.org/jira/browse/SLING-6697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15937341#comment-15937341
]
Timothee Maret commented on SLING-6697:
---------------------------------------
[~amalhotr] AFAIK, reading {{rep:policy}} nodes requires a session with
{{jcr:readAccessControl}} privilege.
Thus, if the service user (e.g. {{sling-tenant}} depending on your mapping)
that computes the list of tenants does not have the {{jcr:readAccessControl}}
privilege under the {{tenant.root}} path ({{/etc/tenants}} by default), then
the {{rep:policy}} will not be listed as a tenant.
Only granting {{jcr:read}} and {{jcr:write}} privileges under the tenant root
to the service user should fix your issue.
> protected nodes show up as tenant in felix console
> --------------------------------------------------
>
> Key: SLING-6697
> URL: https://issues.apache.org/jira/browse/SLING-6697
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Tenant 1.1.0
> Reporter: Ankush Malhotra
>
> Protected nodes for acl also show up as a tenant
> * navigate to /etc/tenants and apply acl and save it
> * rep:policy node was created on /etc/tenants node
> * access tenant console (http://localhost:4502/system/console/tenants)
> Observed:
> rep:Policy node also displayed as a tenant row on tenant console
> Expected:
> rep:policy node should be not displayed
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
