Grouper Users - Open Discussion List

["GW Brown, Information Systems and Computing" <>]

Tom,

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.

Gary

--On 04 April 2007 12:30 -0500 Tom Zeller 
<>
 wrote:

> 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,
> Tom



----------------------
GW Brown, Information Systems and Computing