Grouper Users - Open Discussion List

[Tom Barton <>]

Grouper indeed does not have an incremental change notification 
capability at present, though that is the next substantial area for 
development in the roadmap.

Ldappc can provision grouper groups to an ldap directory. One of its 
core capabilities is computing a "logical diff" to determine the 
incremental changes to be made in the target directory. However, its 
performance in doing so with regard to isMemberOf style of membership 
information has been found too slow in at least one large scale 
experiment. Kathryn Huxtable might comment on that, and on an idea for 
remedying that issue that arose in discussion at the signet-grouper 
combined working group meeting here at the Internet2 conference last Monday.

I'm very open to ideas on how to extend grouper or associated 
applications like Ldappc to facilitate incremental provisioning of group 
changes. Seems like it's just about time to begin those design discussions.

Tom

aragorn wrote:
> Hi,
>
> I'd like to ask, why there is now way how to get information from 
> Grouper API about deleted groups or memberships? Do you have some 
> special purpose (performance, size of database, ...) to not implement 
> this functionality?
>
> We need to propagate changes (CRUD of groups and memberships) made in 
> Grouper to other systems (Sun IDM). I have idea how to "simple" solve 
> this task. Just use another DB where will be archived all groups and 
> memberships and set of classes to update this DB from Grouper. Before I 
> start to implement this I'd like to know if you plan to add this 
> functionality to future releases of core Grouper API or if we can 
> contribute this "extension"?
>
> -----
> Josef Krupicka
> Centre for Information Technology (CIV)
> University of West Bohemia in Pilsen