[
https://issues.apache.org/jira/browse/SLING-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582682#comment-13582682
]
Timothee Maret commented on SLING-2710:
---------------------------------------
"Regarding addPermissions, it is restrict role based access at tenant level
(like having write access for admins/moderators and read access for everybody
else). "
I think this is a rather specific use case, and it would not work since the
TenantProvider#getTenant[s] is using an admin session for retriving tenants
(means the TenantProvider API should change as well).
Maybe you could achieve this by setting the ACL in the content referenced by
the tenant, wdyt ?
> Define TenantManager API
> ------------------------
>
> Key: SLING-2710
> URL: https://issues.apache.org/jira/browse/SLING-2710
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Reporter: Felix Meschberger
> Fix For: Tenant 1.0
>
> Attachments: SLING-2710.patch
>
>
> Tenants currently can only be administered (create, update, remove) through
> the Web Console. In addition the TenantProvider service interface allows for
> looking tenants up (read).
> For administrative purposes it would be good to have a TenantManager service
> interface which allows for these administrative tasks. Something like:
> public interface TenantManager extends TenantProvider {
> Tenant create(String tenantId, Map<String, Object> properties);
> void setProperty(Tenant tenant, String name, Object value);
> void remove(Tenant tenant);
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
