Grouper Developers Forum

[Gagné Sébastien <>]

I’m testing the LDAP with Composite Groups and found something that might be a problem

 

I made a Union Composite Group called udem:CompositeInclude2; It has 4 indirect/effective members as a result of the Union of two groups.

 

The PSP was able to provision the group with the effective memberships, meaning that the AD group has the 4 subject as member, not the 2 composite group. This is what I expected and wanted.

 

The problem come when I turn the LDAP Loader On, I get 4 hibernate exceptions (1 for each member) : http://tinypaste.com/a6c4a9fb

 

It seems the Loader doesn’t properly manage composite groups, maybe it tries to Add a member when it’s not allowed to on this type of object. Is that kind of use case supported with grouper ? What should happen if a member is removed from AD ? Should the component of the composite be modified the reflect the change (i.e. remove the member from the group) ? Delete might be doable, but how would you manage a “add member” for a Union composite ?

 

Deleting the Composite in Grouper resulted in the loader creating a normal group based on the members in the Active Directory.

 

 

Sébastien Gagné,     | Analyste en informatique

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

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