14 Mar
2013
14 Mar
'13
11:38 p.m.
On Thu, Mar 14, 2013 at 11:12 PM, Jerome Velociter <jerome(a)velociter.fr>wrote;wrote:
Hi Denis,
Le 14/03/13 22:59, Denis Gervalle a écrit :
On Thu, Mar 14, 2013 at 9:20 PM, Denis Gervalle <dgl(a)softec.lu> wrote:
You have got it right. This could be improved, and help is welcome. What
happen is that the user groups are evaluated independently to the targeted
entity, and therefore only in the user wiki.
I admit this is a regression, but I have not cross lots of use case like
those. The simple display in admin of Global user in local Group is even
broken (double xwiki:xwiki:...) so this does not seems to me a common usage.
You may provide access to global group in a local wiki to achieve the same
goals.
Hi devs,
This sound like a big regression.
Can you explicit more ? Does this mean that adding a global (main wiki)
user in a local group has no effect ?
We have a new (component based) authorization module since a while now,
and I think 5.0 is the perfect time to introduce it as the default right
service. First, I simply propose to change the default in xwiki.cfg:
xwiki.authentication.**rightsclass=org.xwiki.**security.authorization.**
internal.**XWikiCachingRightService
(Later, I propose that we deprecate that bridge and that we create a
friendly (xwiki oriented) interface over the more generic
org.xwiki.security.**authorization.**AuthorizationManager. But leave
this for a
later proposal.)
So this vote is about changing the default in xwiki.cfg before 5.0M2.
pros:
- improved performance, since the new service is using caching
techniques
and a single page load required lots of calls to it.
- ability for extension to add new rights
- define right declaratively
- separate method for checking and verifying right (throws opposed to
boolean return)
- fix some long waiting bugs like XWIKI-5174, XWIKI-6987, as well as
some unstated ones
Also XWIKI-4550
- possibility to easily solve issues like XWIKI-4491
- no more admin right per default
- being in good position to improve it and release dependencies to
oldcore for security matters.
- possibility for third party to adapt the right settler to their
special
needs (right decision is plugable)
- a consistant right evaluation with very few exception that could be
explained and documented
cons:
- no more admin right per default, but since we have DW, the initial
setup is no more a problem, and advanced users may use superadmin.
- groups are only checked from the user wiki, not from the accessed
entity wiki.
Jérôme
- may exhibit some other minor differences compare to existing
______________________________**_________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/**mailman/listinfo/devs<http://lists.xwiki.org/ma…
--
Denis Gervalle
SOFTEC sa - CEO
eGuilde sarl - CTO
implementation (but mostly consistency fixes)
- test could be improved, critical part (right, settler, data
structure,
cache) are covered at almost 100%, api at 60%, this is probably better
than the old right service
- documentation should be improved, but this is not worse than the old
one anyway
Since I use the new module in all my production servers for several
months
with success, and I really think that if we do not do it now we will
never
go ahead, here is my big +1
WDYT ?
--
Denis Gervalle
SOFTEC sa - CEO
eGuilde sarl - CTO