Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] group membership rules ?

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] group membership rules ?

Chronological Thread 
  • From: Chris Hyzer <>
  • To: Kathryn Huxtable <>
  • Cc: "GW Brown, Information Systems and Computing" <>, Tom Zeller <>, Grouper Users <>
  • Subject: Re: [grouper-users] group membership rules ?
  • Date: Thu, 05 Apr 2007 09:07:46 -0400

Does anyone see something like this to be included in grouper at some point? It seems like a UI to enter a query which would be used periodically sync up with the group registry is useful and would be useful...


Kathryn Huxtable wrote:
At KU we use a loader developed from the XmlImporter class in the API. It
uses SQL queries against our enterprise metadirectory to populate Grouper
groups in a ku:base stem, which can then be combined to form other groups
using the grouper UI. The SQL queries are created from a separate web
interface that we developed.

For downstream provisioning you can use the ldappc product available from
the Grouper website, or if you ask me you can get a copy of my rdbpc, which
provisions tables in a relational database. I should really put this up on
the Grouper wiki in the KU section...


On 4/5/07 3:52 AM, "GW Brown, Information Systems and Computing"


Grouper does not have a 'rules' engine for determining group memberships.
Memberships have to be maintained either by hand i.e. the UI, or by a
'Loader'. In the future there may be membership aging.

I'm sure some kind of rules engine would be very useful but I don't think
there is one on the roadmap at present. It would probably be worth starting
a discussion to gather requirements. In principle, a rules engine could be
developed to use the Grouper API, but otherwise be independent of it. It
could run as a daemon or, perhaps more likely, as a cron job.


--On 04 April 2007 12:30 -0500 Tom Zeller

I'm welcome to ideas regarding how to handle when "something" about a
group member changes that should result in adding or removing (or
disabling ?) the member from the group. For example, given a helpdesk
group which consists of full-time staff and transient student-workers
and which has elevated privileges, is there a Grouper-way to remove a
student-worker from the group when their employment ends ?

I was thinking of something like a group membership rule which says each
member must have a particular attribute.

If I missed something in the docs or wherever please point me in the
right direction.

Thank you,

GW Brown, Information Systems and Computing

Archive powered by MHonArc 2.6.16.

Top of Page