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: Sun, 16 Aug 2015 23:04:27 +0000
- Accept-language: en-US
This is done, give it a try and let me know how it goes. https://bugs.internet2.edu/jira/browse/GRP-1089 Note, in the admin UI where you pick if you are acting like admin or not, will not work with this enhancement, users will always be int he readonly or viewonly
admin group two patches:
grouper_v2_2_1_api_patch_22
grouper_v2_2_1_ui_patch_21 These settings were added to the grouper.base.properties and can be overridden in the grouper.properties
# A viewonly wheel group allows you to enable non-GrouperSystem subjects to act
# like a root user when viewing the registry.
groups.wheel.viewonly.use = false
# Set to the name of the group you want to treat as the viewonly wheel group.
# The members of this group will be treated as root-like users when viewing objects.
groups.wheel.viewonly.group = etc:sysadminViewersGroup
# A readonly wheel group allows you to enable non-GrouperSystem subjects to act
# like a root user when reading the registry.
groups.wheel.readonly.use = false
# Set to the name of the group you want to treat as the readonly wheel group.
# The members of this group will be treated as root-like users when reading objects.
groups.wheel.readonly.group = etc:sysadminReadersGroup
there are two groups on the demo server to test this:
etc:sysadminReadersGroup
etc:sysadminViewersGroup
EveryEntity can view/read/optin/optout of these groups, so anyone can test this by self serve joining / leaving the group. Go to the group in the new UI, click
More Actions, and join/leave From: John Gasper [mailto:]
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.