29 Oct
2003
29 Oct
'03
5:13 p.m.
Hi lukas
I restarted to read SmallWiki code because I lost the changes of my
previous image.
Anyway, if I understand correctly there are permissions and users.
Permission are grants to perform action.
A role contains a list of permissions.
A user play certain roles.
Before performing an action, sw checks whether the user has the right
permissions obtained
by playing a certain role.
Now the structure itself is not involved, this means that if I want to
have a special page that only a certain person can edit but everybody
else cannot I have to create a special role for that. Am I correct? Or
is it possible to grant permission at the instance level like a page?
For example how do I say that a folder can only be edited by admin or
User X, or a person playing the role editFolderX?
Stef
30 Oct
30 Oct
9:22 p.m.
ducasse wrote:
Hi lukas
I restarted to read SmallWiki code because I lost the changes of my
previous image.
Anyway, if I understand correctly there are permissions and users.
Permission are grants to perform action.
A role contains a list of permissions.
A user play certain roles.
correct.
Before performing an action, sw checks whether the user has the right
permissions obtained
by playing a certain role.
Now the structure itself is not involved, this means that if I
want to have a special page that only a certain person can edit but
everybody else cannot I have to create a special role for that. Am I
correct? Or is it possible to grant permission at the instance level
like a page?
well, the structure is also involved:
you can also append a role to a structure: e.g. if a user with role a
wants to perform an action on structure 1, sw will look for role a on
the current structure 1 and apply these permissions. if structure 1
doesn't have role a, sw will look for role a in the parents structure
and so on...
For example how do I say that a folder x can only be edited by admin
or User X, or a person playing the role editFolderX?
- append role editFolderX to folder x with permission to edit.
- append all other roles to folder x and remove permission to edit.
I'll try to integrate my admintool on monday. if you want to have a look
at it (might still have some bugs..):
http://badefix.unibe.ch:8080/?action=AdminAction
...hope this will help.
...the action "admin" doesn't show up yet, so you always have to type
......?action=AdminAction on a certain folder.
cheers,
david.
ps. I'll work on it on friday, so the server might be down.
10:42 p.m.
Hi David,
ps. I'll work on it on friday, so the server might
be down.
I don't know what server you are talking about, but if it is
http://kilana.unibe.ch:9090
bear in mind that this server is used for production stuff, like the
ESE lecture and by Stefan for his lectures and his book. So nothing
should happen to the content at all.
After all, why do you think a Smalltalk server needs to have a
downtime? Adrian and I are selling Smalltalk web-applications to real
customers. One advantage we are used to tell them is that there is
(usually) no server-downtime even during updates.
This is exactly the same for SmallWiki. Change and test the code on
your machine and once you are done download it to the production
machine using your favourite source-management tool. It works even with
StORE, even-tough this is not my favourite source-management tool.
Cheers,
Lukas
--
Lukas Renggli
http://renggli.freezope.org
31 Oct
31 Oct
10:30 a.m.
Lukas Renggli wrote:
Hi David,
cool.
I was talking about the machine I' m developping with. It is not a
productive machine but my latest version is running on it. this machine
is also for other students and they are able to turn it off; or maybe
I'll have to reboot since windows is running on it. that's what I meant
with 'the server could be down'.
cheers,
david.
ps. I'll work on it on friday, so the server
might be down.
I don't know what server you are talking about, but if it is
http://kilana.unibe.ch:9090
bear in mind that this server is used for production stuff, like the
ESE lecture and by Stefan for his lectures and his book. So nothing
should happen to the content at all.
After all, why do you think a Smalltalk server needs to have a
downtime? Adrian and I are selling Smalltalk web-applications to real
customers. One advantage we are used to tell them is that there is
(usually) no server-downtime even during updates.
6 Nov
6 Nov
8:42 a.m.
New subject: admin tool (roles, permissions, users)
hello,
I'm currently working on a webinterface to manage roles, permissions and
users.
prototyp running on http://badefix.unibe.ch:8080
fell free to play around.... (you must login as user admin and click on
link 'Admin')
security features:
- create, delete, modify roles (thy are appended to the current structure)
- create and delete users, set passwords, add roles to a user. (users
are appended to server)
- if the admin gives the admin permissions to a user chief01, the
chief01 can also create roles and users, but can ONLY give those
permissions that he owns himself.
- overview over all users
- overview over all roles in all structures
todo:
- chief01 is still able to administrate to much...
(e.g. manage (add/remove roles, change passwords) users, that
somebody else created)
- ability to collapse (open and close) the folders on the html page
(javascript or server side (session handling))
structures features:
- cut, copy, delete, paste structures
(this is still experimental...)
I' also want to add the zope-concept of beeing able to stop acquiring
permissions from upper tree's objects (structures). therefore I need to
add a new instance variable permissionStrips to class structure. thats
where I want to store all the permissions that shouldn't be acquired.
question to lukas l.,
what do you think. Is this ok and possible for you?
another way would be to add a special role to the structure where I can
store the permissions strips (this is probably a much better way...).
question to alex b.,
I would like to integrate the first version of my tool on friday, but
I'm away from 11 to 5 O'clock in the afternoon. do you have time on
friday morning before 11, or do we start after 5?
cheers and have a great day,
david.
10:35 a.m.
New subject: admin tool (roles, permissions, users)
To play with david admin tool you have to login as admin/smallwiki and
click on the admin
button then security.
stef
On Jeudi, nov 6, 2003, at 08:42 Europe/Zurich, David Vogel wrote:
hello,
I'm currently working on a webinterface to manage roles, permissions
and users.
prototyp running on http://badefix.unibe.ch:8080
fell free to play around.... (you must login as user admin and click
on link 'Admin')
security features:
- create, delete, modify roles (thy are appended to the current
structure)
- create and delete users, set passwords, add roles to a user. (users
are appended to server)
- if the admin gives the admin permissions to a user chief01, the
chief01 can also create roles and users, but can ONLY give those
permissions that he owns himself.
- overview over all users
- overview over all roles in all structures
todo:
- chief01 is still able to administrate to much...
(e.g. manage (add/remove roles, change passwords) users, that
somebody else created)
- ability to collapse (open and close) the folders on the html page
(javascript or server side (session handling))
structures features:
- cut, copy, delete, paste structures
(this is still experimental...)
I' also want to add the zope-concept of beeing able to stop acquiring
permissions from upper tree's objects (structures). therefore I need
to add a new instance variable permissionStrips to class structure.
thats where I want to store all the permissions that shouldn't be
acquired.
question to lukas l.,
what do you think. Is this ok and possible for you?
another way would be to add a special role to the structure where I
can store the permissions strips (this is probably a much better
way...).
question to alex b.,
I would like to integrate the first version of my tool on friday, but
I'm away from 11 to 5 O'clock in the afternoon. do you have time on
friday morning before 11, or do we start after 5?
cheers and have a great day,
david.
5:47 p.m.
New subject: admin tool (roles, permissions, users)
Before 10h it is okay (yes, a bit early :-)
After there is the IOOM lecture.
Alexandre
On Thu, Nov 06, 2003 at 08:42:41AM +0100, David Vogel wrote:
hello,
I'm currently working on a webinterface to manage roles, permissions and
users.
prototyp running on http://badefix.unibe.ch:8080
fell free to play around.... (you must login as user admin and click on
link 'Admin')
security features:
- create, delete, modify roles (thy are appended to the current structure)
- create and delete users, set passwords, add roles to a user. (users
are appended to server)
- if the admin gives the admin permissions to a user chief01, the
chief01 can also create roles and users, but can ONLY give those
permissions that he owns himself.
- overview over all users
- overview over all roles in all structures
todo:
- chief01 is still able to administrate to much...
(e.g. manage (add/remove roles, change passwords) users, that
somebody else created)
- ability to collapse (open and close) the folders on the html page
(javascript or server side (session handling))
structures features:
- cut, copy, delete, paste structures
(this is still experimental...)
I' also want to add the zope-concept of beeing able to stop acquiring
permissions from upper tree's objects (structures). therefore I need to
add a new instance variable permissionStrips to class structure. thats
where I want to store all the permissions that shouldn't be acquired.
question to lukas l.,
what do you think. Is this ok and possible for you?
another way would be to add a special role to the structure where I can
store the permissions strips (this is probably a much better way...).
question to alex b.,
I would like to integrate the first version of my tool on friday, but
I'm away from 11 to 5 O'clock in the afternoon. do you have time on
friday morning before 11, or do we start after 5?
cheers and have a great day,
david.
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.iam.unibe.ch/~bergel
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
5:55 p.m.
New subject: admin tool (roles, permissions, users)
Hi David,
I' also want to add the zope-concept of beeing
able to stop acquiring
permissions from upper tree's objects (structures). therefore I need
to add a new instance variable permissionStrips to class structure.
thats where I want to store all the permissions that shouldn't be
acquired.
question to lukas l.,
what do you think. Is this ok and possible for you?
another way would be to add a special role to the structure where I
can store the permissions strips (this is probably a much better
way...).
I think we should discuss this next monday. I've never used and
understood that concept, even-tough I have built a lot of Zope
applications with different security concepts. It would be great if you
could explain your motivation and present a prototype ...
Cheers,
Lukas
--
Lukas Renggli
http://renggli.freezope.org
6:29 p.m.
New subject: admin tool (roles, permissions, users)
On Jeudi, nov 6, 2003, at 17:55 Europe/Zurich, Lukas Renggli wrote:
Hi David,
Yes excellent idea.
I would like to understand (david you can sell that as a possible
implementation alternative)
I' also want to add the zope-concept of
beeing able to stop acquiring
permissions from upper tree's objects (structures). therefore I need
to add a new instance variable permissionStrips to class structure.
thats where I want to store all the permissions that shouldn't be
acquired.
question to lukas l.,
what do you think. Is this ok and possible for you?
another way would be to add a special role to the structure where I
can store the permissions strips (this is probably a much better
way...).
I think we should discuss this next monday. I've never used and
understood that concept, even-tough I have built a lot of Zope
applications with different security concepts. It would be great if
you could explain your motivation and present a prototype ...
Cheers,
Lukas
--
Lukas Renggli
http://renggli.freezope.org
10:14 p.m.
New subject: admin tool (roles, permissions, users)
what do you think. Is this ok and possible for you?
another way would be to add a special role to the structure where I
can store the permissions strips (this is probably a much better way...).
ok, I removed the instance variable from the structure to make it
compatible with the current running system. I put all the needed
information in a role called barrier.
alex and I will put this version up tomorrow.
cheers,
david
30 Oct
30 Oct
10:31 p.m.
Hi Stef,
sorry that I could not replay the last days, I have too much other
things to do right now. Yesterday night I started trying to fix some of
the bugs and suggestions made during that week, but I could not finish
yet.
Also I have problems reproducing the Swazoo bug, as I cannot download
the whole package from Cincom into a new image. After about 10 or 20
minutes I get a timeout before it has been loaded completely. When
updating to the latest version of Swazoo in my development image, no
bug occurs; but the updating doesn't seem to work as I don't have a
class called HTTPPostDataArray and the message #keysAndValuesDo: works
properly.
Anyway, if I understand correctly there are
permissions and users.
Permission are grants to perform action.
A role contains a list of permissions.
A user play certain roles.
The class diagram looks like this:
SecurityInformation
A
|
+-----------------------+--------------------------+
| | |
| | |
User (1) -------> (1..) Role (1) -------> (1..) Permission
Users are defined in the server class. Existing roles are just the
union of all roles assigned to all the users in the system. The
comparison #= of Roles and Permission is done using their name.
When processing a query, e.g. /a/b?action=MyAction, the following
actions are taken:
- The server is looking for a username and password given in the
request header. The username is looked-up in the server and checked if
the password matches, if so a copy of that user is assigned to the
current request. If there is no authentication given or if the
authentication does not match, the anonymous-user is assigned
automatically.
- As you know, the chain-of-responsibilities is started and the request
is passed to the root structure. Every structure has the possibility to
redefine roles. If there is the role X defined in the root folder and
the user of the current request has got the role X defined too, then
the role of the user is replaced with the role of the structure. This
happens for all the roles of the user, if there are any redefinition in
the structure.
- It is important to understand that during processing there are roles
added or removed from the user, existing roles are just replaced with
roles having the same name but contain different permissions.
- The request with the updated user is then passed to next child within
the chain, etc.
- At the of the chain the given action (if there is nothing given, the
default action will be executed) is execute. By default actions have
the possibility to override the message #executePermission to assert
the permissions the user needs to execute it. If such an an permission
fails, the actions is aborted and error action is executed instead.
Now the structure itself is not involved, this means
that if I want to
have a special page that only a certain person can edit but everybody
else cannot I have to create a special role for that. Am I correct? Or
is it possible to grant permission at the instance level like a page?
Just define the anonymous role in that structure without the
edit-permissions.
Hope that helps,
Lukas
--
Lukas Renggli
http://renggli.freezope.org
7476
days inactive
7484
days old
10 comments
5 participants
participants (5)
-
Alexandre Bergel -
david vogel -
David Vogel
-
ducasse -
Lukas Renggli