Skip to Content.
Sympa Menu

grouper-users - ldappc and nonexistent members-name-list ?

Subject: Grouper Users - Open Discussion List

List archive

ldappc and nonexistent members-name-list ?

Chronological Thread 
  • From: "Tom Zeller" <>
  • To: "" <>
  • Subject: ldappc and nonexistent members-name-list ?
  • Date: Tue, 10 Jun 2008 10:42:56 -0500
  • Domainkey-signature: a=rsa-sha1; c=nofws;; s=gamma; h=message-id:date:from:sender:to:subject:mime-version:content-type :x-google-sender-auth; b=wYstHgdEuVPv3NiJLMkyFjrFmMCGHXJ100tVdnYVcLuOknZhWpZeF4/FVAoScub20P HItg3s7BGmV2Luz+2nnszltJSWyeyx8aFJR4Rl/DBL5eNVNjswYAR+yJg05kIcbZZW7T qhrqlqgQgoiyR8t8GBFMDXKxt5Qe3n2ZVnRaM=

I've found that if a group member does not exist in the provisioned ldap directory, then ldappc won't provision members-dn-list, but it will provision members-name-list, e.g. :

dn: cn=group,...
hasmember: subjectA
hasmember: subjectB
member: cn=subjectA, ...

where cn=subjectB,... does not exist, given 

<group-members-dn-list list-object-class="groupOfNames" list-attribute="member" list-empty-value=""/>

<group-members-name-list list-object-class="eduMember" list-attribute="hasMember" >

In our usage, it would be 'more consistent' for members-name-list to not be provisioned if members-dn-list is not provisioned. Am I making sense ? Is there a way to make members-dn-list and members-name-list always match ?


Archive powered by MHonArc 2.6.16.

Top of Page