Grouper Users - Open Discussion List

[Colin Hudler <>]

Colin Hudler wrote:

<snip>
> Just after, while iterating through the LDAP results, it builds a list 
> of subjects that will need the list-object-class
>        if (hasObjectClass) {   
> subjectObjectDns.add(subjectDn.toString()); }
>
> Later on up the chain, the provisioner will use subjectOBjectDns to 
> modify the LDAP entry (attempt to add the objectclass).  What I don't 
> understand is how it can trust that set, since it was only built off 
> of the query that will return exactly those entries that have an 
> ismemberof value.  When list-object-class is null it throws the error, 
> otherwise it tries to add the objectclass and gets an LDAP operations 
> error.  I tested up to 1.2-SNAPSHOT.
Sorry.  What I mean here is that subjectObjectDns is used as a those 
that do *not* need the objectclass.  Any member not matching the filter 
"(&(uid=*)(ismemberof=*))" would have an attempted modification to their 
objectclass.