Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] Setting group ACLs based on stem?

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] Setting group ACLs based on stem?

Chronological Thread 
  • From: Peter DiCamillo <>
  • To: Chris Hyzer <>
  • Cc: "" <>
  • Subject: Re: [grouper-users] Setting group ACLs based on stem?
  • Date: Tue, 28 Sep 2010 12:57:19 -0400

The group BROWN:ADMIN:COURSE has as its membership two other groups. In Grouper 1.6.1, I was able to add a person to one of those other groups in less than a minute. However, when I tried deleting one of those groups from BROWN:ADMIN:COURSE (also in 1.6.1) it took 12 hours. Fortunately, that's not something I would ever normally need to do.

I thought I had seen some reference to ACLs being inherited from stems, I guess it was for Grouper 2.0. Thanks for the info.


Chris Hyzer wrote:
When you say it takes hours, you mean an old version of grouper right?
In 1.6.1, it should be faster since the effective memberships are not stored
in their own row in a table.
In 2.0 there is a way to put a rule on a stem, which would help as well (in
that if you create a group under that stem you don't have to assign whatever
privileges are in the stem). It will have good performance too.


-----Original Message-----

On Behalf Of Peter DiCamillo
Sent: Saturday, September 25, 2010 4:59 AM

Subject: [grouper-users] Setting group ACLs based on stem?

We have about 475K groups for course sections (they go back to 2007), and they're all under the stem BROWN:COURSE. Certain administrators need to be able to modify those groups, so each of those groups has an admin ACL for the group BROWN:ADMIN:COURSE. That works, but making a change to the membership of BROWN:ADMIN:COURSE can take hours to complete. In Grouper 1.6.1, is there a way to specify a single ACL that would apply to all groups under BROWN:COURSE? If so, would that allow BROWN:ADMIN:COURSE to be updated quickly, or is there some other solution?


Archive powered by MHonArc 2.6.16.

Top of Page