Grouper Users - Open Discussion List

[Kathryn Huxtable <>]

One problem with using subject attributes to generate rules-based groups
within grouper is that the subject API would need substantial development to
be able to do this efficiently with various source adapters.

Since the subject API is the upstream interface between your IdMS and
Grouper it needs to be general, not specific. Given the loose coupling
between the IdMS and Grouper this may be a difficult problem to solve within
Grouper.

That's why we wrote an external loader at KU.

-K

On 4/5/07 7:29 AM, "Tom Barton" 
<>
 wrote:

> Just to expand a bit, the original conception of the grouper project
> included a "stream loader", that rules-engine-enabled external task that
> could maintain memberships in synchrony with external attributes. But
> we've never had the resources to do other than focus on the core of the
> work: group management capabilities.
> 
> I'm hoping that as sites now actually begin to use grouper, we'll see
> loaders being developed that are more general than a one-trick pony. In
> other words, I'm still looking to the community to provide the resources
> lacking in the grouper project per se that are needed to complete the
> group management toolkit.
> 
> GW Brown, Information Systems and Computing wrote:
>> 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
>>