Skip to Content.
Sympa Menu

grouper-users - [grouper-users] RE: Incremental memberships update in Loader jobs

Subject: Grouper Users - Open Discussion List

List archive

[grouper-users] RE: Incremental memberships update in Loader jobs

Chronological Thread 
  • From: Gagné Sébastien <>
  • To: "Chris Hyzer" <>, <>
  • Subject: [grouper-users] RE: Incremental memberships update in Loader jobs
  • Date: Wed, 20 Jun 2012 11:59:15 -0400

Using the example below


UserA-B-C is in the Grouper Group

UserA-B-D is in the Source


The loader gets UserA-B-D, sees that UserA and UserB already exist in Grouper, but not UserD, so it adds a membership for UserD. It could ignore UserC


I remember seeing things about _systemOfRecords, but didn’t get the purpose of it, but now it might be usefull, I’m kind of afraid of the quantity of groups the user will see (the composite, the system of records and the Add group), maybe these are hidden from view. I’ll check the video and and the composites to see if it answers our need.


Thank you


De : Chris Hyzer [mailto:]
Envoyé : 20 juin 2012 11:52
À : Gagné Sébastien;
Objet : RE: Incremental memberships update in Loader jobs


How will it know which members are removed from ldap and which are added to ui?

In any case, I think the load is intended to manage “system of record” groups.  If you need people to do ad hoc changes, you should mark the job as “add include/exclude” type, which will create an overall group, an additions group, a subtractions group, and setup the composites appropriately.  In the loader job you can add that type automatically (we do this with org groups).  If you need help let me know.





From: On Behalf Of Gagné Sébastien
Sent: Wednesday, June 20, 2012 11:41 AM
Subject: [grouper-users] Incremental memberships update in Loader jobs



I was wondering if there was a way to have « incremental » (add only?) membership updates in the Loader Jobs (LDAP and SQL both behave the same). Right now, using the UI, if I add a member to a Grouper Group that is managed by a loader it will be removed the next time it runs.


Here is my current use case :

1.       GroupABC is in Grouper and managed by a loader process

2.       Loader adds UserA and UserB as member of GroupABC
{{ GroupABC contains: UserA, UserB }}

3.       Using Grouper UI, I add UserC to GroupABC
{{ GroupABC contains : UserA, UserB, UserC }}

4.       Loader process runs, removes UserC
{{ GroupABC contains : UserA, UserB }}

5.       I add UserD in source (e.g. Active directory or SQL database)

6.       Loader process runs, adds UserD
{{ GroupABC contains : UserA, UserB
, UserD }}


Is there a way for us to have UserA-B-C-D in GroupABC  using the loader processes ? Is there a flag saying “only add new/missing members and ignore the other additionnal Grouper member” , i.e., don’t do step #4 ( keep/ignore UserC) and still add UserD in #5 ?


This can mostly be done if were dealing with an LDAP source since real-time provisioning will likely send UserC in the source before the LDAP Loader runs. When it will run, the loader will have UserC in its result set so it will leave it in the Group.





Sébastien Gagné,     | Analyste en informatique

514-343-6111 x33844  | Université de Montréal,

                     | Pavillon Roger-Gaudry, local X-100-11


Archive powered by MHonArc 2.6.16.

Top of Page