[
https://issues.apache.org/jira/browse/OFBIZ-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260384#comment-13260384
]
Pierre Smits commented on OFBIZ-4836:
-------------------------------------
Hi Sascha,
I am not that well experienced with Jackrabbit, but I would say that the best
solution would be similar to multi-tenancy in OFBiz. There we set up for each
tenant a different set of databases. For that we use the tenantID as the
delegator. And the security is fairly straight-forward. Only tenant users (in
accordance with the security schema for him/her) have access to their own
tenant data, and perform actions/functions accordingly.
That should also work with JCR, i think. But I might be mistaken.
Wouldn't creating tenants as nodes introduce the issue (risk?) of a user of a
higher node having access to data in lower nodes? That would be hard to sell to
(potential) customers.
What if there was a repository for each tenant? Is that feasible?
Regards,
Pierre
> Jackrabbit (jcr) doesn't work nice with multi-tenancy aspect of OFBiz
> ---------------------------------------------------------------------
>
> Key: OFBIZ-4836
> URL: https://issues.apache.org/jira/browse/OFBIZ-4836
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework
> Affects Versions: SVN trunk
> Reporter: Pierre Smits
> Priority: Blocker
> Fix For: SVN trunk
>
>
> When having multiple tenants and one of the users (of a tenant) creates
> (uploads) a file to JCR then this file is visible to all users of all tenants
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
