[Zope] Zope concepts

Tue, 23 May 2000 06:29:14 -0400

--============_-1253044734==_ma============
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

>I intend to build an intranet with zope...though it's not as simple 
>as that...I'd like 90% of the site to be password protected (giving 
>access to members of my company)...do I use acl_users for this?

Yes or any of the other models (UserDB, etc)

>I'd also like parts of the site to be accessible (and maybe 
>manageable albeit minimally) by clients....Do I have to create a 
>second user/access model for this or can I use the acl_users to do 
>this for me too.

Yup. Create a role for them and limit that role.

>I'm having problems
>     a. Making the acl_user stuff work...I can either login as admin 
>or not all.
     and b. Getting to grips with the concept of the user/privs/access 
model in acl_users

Create a user, give them a role and they will inherit all of the 
access levels of that role. Create a new role and give that role 
different access levels and you can manage it better through the role.

It is not that much different than most user/group/role access 
scenarios, in that once you get started using it and understand the 
basic concepts it will all fit.

Remember that users inherit permissions from parent objects which you 
can turn off if that model does not suit you.

J
--============_-1253044734==_ma============
Content-Type: text/html; charset="us-ascii"

<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { margin-top: 0 ; margin-bottom: 0 }
 --></style><title>Re: [Zope] Zope concepts</title></head><body>
<blockquote type="cite" cite><font size="-1" color="#000000">I intend
to build an intranet with zope...though it's not as simple as
that...I'd like 90% of the site to be password protected (giving
access to members of my company)...do I use acl_users for
this?</font></blockquote>
<div><br></div>
<div>Yes or any of the other models (UserDB, etc)<br>
</div>
<blockquote type="cite" cite><font size="-1" color="#000000">I'd also
like parts of the site to be accessible (and maybe manageable albeit
minimally) by clients....Do I have to create a second user/access
model for this or can I use the acl_users to do this for me
too.</font></blockquote>
<div><br></div>
<div>Yup. Create a role for them and limit that role.</div>
<div><br></div>
<blockquote type="cite" cite><font size="-1" color="#000000">I'm
having problems</font></blockquote>
<blockquote type="cite" cite><font size="-1"
color="#000000">&nbsp;&nbsp;&nbsp; a. Making the acl_user stuff
work...I can either login as admin or not all.</font></blockquote>
<div><font size="-1" color="#000000">&nbsp;&nbsp;&nbsp; and b.
Getting to grips with the concept of the user/privs/access model in
acl_users</font></div>
<div><br></div>
<div>Create a user, give them a role and they will inherit all of the
access levels of that role. Create a new role and give that role
different access levels and you can manage it better through the
role.</div>
<div><br></div>
<div>It is not that much different than most user/group/role access
scenarios, in that once you get started using it and understand the
basic concepts it will all fit.</div>
<div><br></div>
<div>Remember that users inherit permissions from parent objects
which you can turn off if that model does not suit you.</div>
<div><br></div>
<div>J</div>
</body>
</html>
--============_-1253044734==_ma============--