Skip to Content.
Sympa Menu

grouper-users - Re: Re: [grouper-users] Ldappc missing LDAP sourced members

Subject: Grouper Users - Open Discussion List

List archive

Re: Re: [grouper-users] Ldappc missing LDAP sourced members

Chronological Thread 
  • From: "Tom Zeller" <>
  • To:
  • Cc:
  • Subject: Re: Re: [grouper-users] Ldappc missing LDAP sourced members
  • Date: Tue, 18 Nov 2008 18:59:39 -0600
  • Domainkey-signature: a=rsa-sha1; c=nofws;; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:references:x-google-sender-auth; b=pTMHppGgCnxxue/0aSWHtfispi7qAuSmNn28/3bTRJyERKk+vokuYrEVoww9GbpEk0 Rc1WUE0cWa5zADA3Ki9P0Q2iFPjOICYHdnnQmKcZ02+8p7adEDndCe79Eq2rzjhA2YND TqYFMT/8+J9Q1vgMKACx2qQCoLG+O7NtCGAMA=

I'll second guess replacing subject-attribute="id" with ="uid" for the NAU LDAP source.

On Tue, Nov 18, 2008 at 5:38 PM, <> wrote:

In my tests today, I have removed the group-members-dn-list in lieu of just getting names into uniqueMember. With the 4 sources stated in my original email, only the g:gsa source populates in LDAP (creates uniqueMembers of the groups within groups.)

<source-subject-name-map source="g:isa" subject-attribute="id" />
<source-dubject-name-map source="NAU LDAP" subject-attribute="id" />
<source-subject-name-map source="jdbc" subject-attribute="id" />
<source-subject-name-map source="g:gsa" subject-attribute="name" />

I've also moved over the sources.xml from the grouper-api/conf so that it takes advantage of the exact source info as the working API does. I assume that ldappc will just be taking advantage of this when bundled(?) Alas, this shows no different results.

Archive powered by MHonArc 2.6.16.

Top of Page