Grouper Users - Open Discussion List

[Tom Zeller <>]

I suggest that you drop

 <group-attribute-map group-attribute="UID" ldap-attribute="riceGrouperID" />

since the UID or UUID or id attribute of a group is not available to ldappc here.

And, since I would think that rdn lookups are faster than givenName, which might be indexed differently, in

<source-subject-identifier source="g:gsa" subject-attribute="name" initial-cache-size="100003"> <ldap-search base="ou=pengletest,dc=rice,dc=edu" scope="subtree_scope" filter="(givenName={0})" />

</source-subject-identifier

replace filter="(givenName={0})" with filter="(cn={0})".

How many memberships do you have ? e.g. how many rows are in the grouper_memberships table: select count(*) from grouper_memberships ?

The latest 1.4 branch of grouper has some performance improvements to ldappc, such as not returning all attributes from subjects when not needed. We talked about releasing 1.4.2 in a few weeks which would incorporate these improvements if you don't want to build from source. It would be interesting to see if 1.4.2 was faster.

TomZ

> I've tried various configurations of ldappc.xml.
> This  is the latest attempt. It works, but doesn't populate
> riceGrouperID; instead I get a warning in the logs like this:
>
> 2009-05-12 15:10:47,013: [main] WARN  ErrorLog.warn(95) -
> [edu.internet2.middleware.ldappc.synchronize.GroupEntrySynchr
> onizer]  GROUP[[ DISPLAY NAME = Stem for testing:Test
> Courses:ELEC526:Spring 2009:Section 001:Instructor ][NAME =
> testStem:courses:ELEC526:Sp09:001:instructor][UID =
> 7cfc2e80-574e-4107-ac89-564cb7de041c]] field not found: UID
>
>   -paul
>
> - --On Tuesday, May 12, 2009 4:17 PM -0500 Tom Zeller
> <> wrote:
>
>> Could you please either post or send privately sanitized
>> copies of ldappc.xml and sources.xml used by ldappc ?
>>
>>
>> TomZ
>>
>>
>> On Tue, May 12, 2009 at 3:27 PM, Paul Engle <>
>> wrote:
>>
>> All,
>>   I'm seeing some pretty slow initial load times for ldappc,
>> and I assume it's because something is not optimized in my
>> configuration. I seem to recall that it is desirable to store
>> the subject_id from grouper in LDAP so that group subjects
>> can be retrieved without an additional lookup. I was
>> assuming I could do this with ldappc via a
>> group-attribute-mapping, but I can't figure out what
>> attribute name from grouper to use. There's nothing defined
>> in grouper_fields in the database that seems to have that
>> info. Should I be doing this another way? Any pointers would
>> be welcome.
>>
>>   The grouper hierarchy we've designed relies heavily on
>> member
>> groups, and I'm assuming that's what's slowing down the
>> provisioning. It's taking upwards of 16 hours to do an
>> initial load of about 15500 groups. We're running a pretty
>> basic grouper-1.4.1 installation with no custom hooks.
>>
>>   -paul