[Zope] Zope Member Log In behavior

[Jonathan Cyr]

The folders are stuctured...

- Common
     - Member 1
     - Member 2

I'd like to provide a login at the Common folder, and drop the member 
in their Member folder.  Each user has an user def entry in their 
Member folder only.  If I put each user in the Common folder, they'll 
have access to all of the member folders, not just theirs.

My system works fine today... members just have to browse to their 
Member page and login there... then all is fine... I was hoping to 
provide one login for all members, one folder up.  Hoping for an 
iterator of some kind.

Hopefully clearer,

-Jon


Chris Withers wrote:

> Jonathan Cyr wrote:
> 
>> Here's what I'm trying to do.  My website/app has a common folder to 
>> which members have view only access, then inside this common folder, 
>> each user member has their own folder with significantly more access.
> 
> 
> I do hope that access is provided by local roles?
> 
>> What I'm hoping to do is provide a common login in the common folder, 
>> that somehow iterates through the member sub-folders and logs them in 
>> there.  (Note: the member sub-folders are folderish python products of 
>> my own design)
> 
> 
> How are you folder stuctured?
> 
> /common
> /member1
> /member2
> 
> or:
> 
> /common
> /common/member1
> /common/member2
> 
> ?
> 
> The second option is probably better for you here...
> 
>> I'm trying to avoid giving each user rights to the common folder and 
>> preventing acquistion of the user folder through each member folder if 
>> I can.
> 
> 
> Why?
> 
> If the users don't have the permissions needed to do aything with the 
> userfolder, then what's the problem?
> 
> Why don't you give the 'Authenticated' role the 'Access contents 
> information' role in the common folder, and then give each member the 
> 'Manager' role as a local role in their member folder?
> 
>> Any magic Zope-ish way to do such a thing?
> 
> 
> No magic, just learn a bit more about role to permission mapping and 
> lcoal roles. Maybe proxy roles too if required...
> 
> Chris
>