Re: Sharing membership between different Plone sites

Hi,

Please see my comments inline:


>
>> 1. The good news is that the roles that are not part of the default
>> Zope-users-system (like reviewer, editor - Zope thinks only in terms 
>> of
>> manager, owner etc.) can be added on the Zope-level. They don't make 
>> a lot
>> of sense there, but Plone inherits them and Plone does understand 
>> their
>> significance. What I mean is that when a user is a reviewer on the
>> Zope-level, which doesn't mean anything to Zope, then he is also a 
>> reviewer
>> on the Plone-level, because Plone inherits the user properties from 
>> Zope's
>> acl_users, and Plone understands "reviewer" as "someone who is a Plone
>> reviewer", which is a very good thing.
>
> This means that a Member would have the same roles
> in all sites: those assigned in Zope's acl_users,
> right? Or can we override this on the site level?

That is an essential point. We do not want to lose the GRUF usability. 
I do believe GRUF is usable outside Plone.
Also, a person who is a reviewer on one site, maybe is just a regular 
member on another site.

Common login should not automatically indicate common roles among sites.

>
>> 2. The not-so-good-news is that we are losing the 
>> Group-aware-User-Folder
>> stuff, since that is a Plone feature and not a Zope feature. Maybe I 
>> can
>> comfort Priyadarshan here a little by mentioning that we could have a
>> different architecture for us (developers, editors etc.) and the 
>> public,
>> using Plone's user system for us and Zope's user system only for the 
>> public,
>> since it is the public's membership issue that we concerned with 
>> anyway, and
>> who wants to put them into different groups?
>> - By the way, if anybody thinks he's just got a very smart idea: why 
>> don't
>> we put all our Plone sites into one big Parent-Plone-Site, with the 
>> Parent
>> containing an acl_users file (which would then automatically be a
>> Plone-based Group-aware-User-Folder-acl_users file) and which would 
>> be the
>> one that all the children Plone sites inherit from, ---- forget it. 
>> Doesn't
>> work.
>
> Ok. Site Administrators, Editors, Designers in the individual
> Plone Site acl_users. Members and Anonymous Users in Zope's
> acl_users in the root of the public Zope instance(s) filestorage.
>
> Let's assume that a Member is known in Zope's acl_users.
> If that Member logs in to srichinmoy.org, and then points
> his browser to srichinmoyraces.org, does he have to log
> in again?
>

Common login means that I have same login and same password. If the 
session is based on the domain name, I would have to relogin if i type 
the address in the bar.
But maybe using cookies this can be avoided. Cookies can be shared by 
many sites.



priyadarshan
Vasudeva Server


--------------------------------------------------------------------------
This message is sent to you because you are subscribed to the mailing list <VasudevaService-K9y3B4ipJAZZAIG4hdpdiNBPR1lH4CV8@public.gmane.org>.