for us the goal would be to run multiple customers in one sling instance
without the ability to touch the code/content of any other tenant. It
would be nice if
a) restricting users from one tennat to another would be simple
b) allow a good search path override for each tenant
c) split out the admin account into tenants (an admin session should not
have access to all tenants)
d) osgi properties per tenant (probably needs to be handled in felix?)
Ruben
On 8/11/2014 6:29 AM, Bertrand Delacretaz wrote:
Hi,
On Mon, Aug 11, 2014 at 3:13 PM, Stefan Seifert <sseif...@pro-vision.de> wrote:
...btw. we should perhaps first start to define what we mean with the term
"tenant". this much-used and
overloaded term might be a source of confusion as well...
Definitely - I suggest creating a page under
https://cwiki.apache.org/confluence/display/SLING for multi-tenant use
cases and definitions.
-Bertrand
