When the <source-subject-name-map subject-attribute="id|name" ...>, ldappc would not always provision the subject since subject.getAttributeValue("id|name") may return null for the supplied source/subject adapters. Now ldappc calls subject.getId() or subject.getName() if appropriate after trying subject.getAttributeValue().

— From grouper-users ----

Revisiting this ancient issue with a better understanding...

Currently have provisioning of "group-members-dn-list" working and now
trying to add "group-members-name-list" via the "name" attribute. The
provisioning of "group-members-name-list" does not seem to be working
correctly. My config seems to be properly setup:

<group-members-dn-list list-object-class="nauEduEnterpriseGroup"
list-attribute="nauEduManualMember"/>

<group-members-name-list list-attribute="memberUid" list-object-
class="nauEduEnterpriseGroup" list-empty-value="NONE">
<source-subject-name-mapping>
<source-subject-name-map source="NAULDAP" subject-attribute="name" />
</source-subject-name-mapping>
</group-members-name-list>

I have confirmed my source:
source: id='NAULDAP' name='NAU LDAP'
class='edu.internet2.middleware.grouper.subj.GrouperJndiSourceAdapter'

I have confirmed the attribute on the subjects to be populating:
subject: id='XXXXXXXXXXXXXXXXXXXXXXXXXX' type='person'
source='NAULDAP' name='rdw4'

All I get is the empty value "NONE" populated for attribute
"memberUid" in LDAP for all groups (populated or not) when
provisioning. Any ideas on this?

Raymond Walker
Software Systems Engineer Sr.
ITS Northern Arizona University