Grouper Users - Open Discussion List

[Kathryn Huxtable <>]

The problem, as I mentioned in another message, is that the subject API
provides only loose coupling with your IdMS data.

Since I'm doing subject API development and will be discussing this with
Lynne, Tom, and the other developers at the I2 members meeting, maybe we can
add that ability as a direction we want to go.

I'll think on it...

-K


On 4/5/07 8:07 AM, "Chris Hyzer" 
<>
 wrote:

> 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...
> 
> Chris
> 
> 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...
>> 
>> -K
>> 
>> 
>> On 4/5/07 3:52 AM, "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
>>> 
>>>     
>> 
>>