stanbol-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Fabian Christ <>
Subject Re: It's not security, but rather multi-user vs. single-user Stanbol
Date Mon, 08 Apr 2013 12:47:46 GMT

I am not sure if this is the right distinction but it is inline with
my interpretation. Let's give people (users) the power to easily
deactivate (remove bundles) that they do not want for their use case.
Or to express it in a positive way: Let users select the features they

The other question would be what scenarios are we testing against in
our integration tests. At the moment we are only testing the single
user scenario.

2013/4/8 Bertrand Delacretaz <>:
> Hi,
> I'm trying to understand the disconnect that we're seeing in the
> security discussions...isn't that more about the following two modes
> of using Stanbol?
> Single user Stanbol:
> A stateless engine that's accessed by trusted systems, which are
> supposed to handle security and access control by themselves
> Multi-user Stanbol:
> An engine that's accessed by non-trusted users and might store their
> data, so needs security features, user management, etc.
> Agreeing on these two usage modes might help us have more constructive
> discussions, IMO, about features that multi-user requires but
> single-user doesn't even want to see.
> -Bertrand


View raw message