grouper-users - RE: [grouper-users] RE: Priv Hook?
Subject: Grouper Users - Open Discussion List
List archive
- From: Chris Hyzer <>
- To: John Gasper <>, grouper-users <>
- Subject: RE: [grouper-users] RE: Priv Hook?
- Date: Wed, 26 Aug 2015 21:50:21 +0000
- Accept-language: en-US
I think a generic hook (or rule)/attribute for this would be a good idea. Did you end up implementing this? Is there code you can share? Thanks Chris From: John Gasper [mailto:]
One more similar scenario that I’d like to get your thoughts on. By using an attribute at the stem (and essentially be inherited by all child stems) level or on a group, grant the groups opt out to “self”, so users within this
part of the tree can always remove themselves from a group. We were going to using a hook to add the “optout” for self priv to the group if the stem or any part of the its tree has the attribute, and a second hook that prevents an group admin from removing
the priv. Thoughts on that? I think what we are seeing from schools is a desire to apply inherited permissions that can’t be changed by a stem or group admin. Similar to how the Windows
permissions can work. Thanks, John -- John Gasper From:
<> on behalf of John Gasper <> Yes, I think we can commit to doing testing with this. Thanks, John -- John Gasper From:
<> on behalf of Chris Hyzer <> If you have READ then you automatically have VIEW, so you don’t have to assign both. Also, I think you might have performance problems with this on large registries… I looked in the code and to add the ability to have a READONLY and VIEWONLY
wheel group would not be a lot of changes. I can do some testing, but if you can also test that would be great. Is that something you are interested in? Thanks, Chris From: John Gasper []
At the end of the day, we want a read-only “wheel” group… In other words a group whose members can view, but not change all groups and their memberships. The
proposed method of implementation is to use a post hook at give “view" and “read" to a newly created group… and prevent “view" and “read" from being removed from a group (except perhaps by someone in the Wheel group). -- John Gasper From:
<> on behalf of Chris Hyzer <> You should be able to use a membership hook, since privileges are implemented at memberships. The list type is “access”, and you can see which priv it is,
and who is removing it, and veto it. If you write up exactly what you are doing I can look into making the grouper “rules” more full featured since these types of things should be easily accomplished with rules. Thanks, Chris From: John Gasper []
There specific case I’m working on is this… We are assigning privs (allow specific group to read and view) to new created groups via a hook. That part is great.
We don’t want Group Admins to be able to remove that priv. -- John Gasper From:
<> on behalf of Chris Hyzer <> Yes, can you tell me more info about what you want to do?
J Thanks, Chris From:
[]
On Behalf Of John Gasper Is there a hook to veto the assignment/deletion of a privilege? -- John Gasper |
- Re: [grouper-users] RE: Priv Hook?, John Gasper, 08/03/2015
- Re: [grouper-users] RE: Priv Hook?, John Gasper, 08/03/2015
- RE: [grouper-users] RE: Priv Hook?, Chris Hyzer, 08/26/2015
- RE: [grouper-users] RE: Priv Hook?, Chris Hyzer, 08/16/2015
- Re: [grouper-users] RE: Priv Hook?, John Gasper, 08/18/2015
- Re: [grouper-users] RE: Priv Hook?, John Gasper, 08/03/2015
Archive powered by MHonArc 2.6.16.