Grouper Users - Open Discussion List

[Tom Zeller <>]

Very vanilla.

Querying ldap, for subjects (in grouper) and for member identifiers
(in ldappcng), probably takes the most time.

I need to implement caching in ldappcng, probably by implementing the
TTL-based <ResultCache /> in the spml data connector similarly to the
ldap and rdbms data connectors.

However, ldap lookups are likely doubled if you are using the ldap or
jndi source adapters. So, a single caching ldap instance which is both
a source adapter and spml target would probably help the most.

I can attempt a single class which implements a grouper source adapter
and an ldappcng target.

Comments ?

[1] https://spaces.internet2.edu/display/SHIB2/ResolverLDAPDataConnector

On Thu, Mar 17, 2011 at 3:37 PM, Lynn Garrison 
<>
 wrote:
> Tom,
>        I have attached the two files.  We switched to using the University 
> of Washingtion ldap source adapter for the latest run.  The times are about 
> the same.  The configuration have minor changes from the example file.
>
>        The ldappc-resolver.xml  has a members-psu-person defined. We are 
> using the uid as the id for the source.
>        The stem provision was deleted from the ldappcng.xml file.
>
> Lynn
>
>
> On Mar 16, 2011, at 7:00 PM, Tom Zeller wrote
>
>>>> Shall we pursue how to speed up your instance of ldappcng ?
>>
>>>   Yes we would like to explore speeding up ldappcng.  What information 
>>> would you like me to provide?
>>
>> Let's start with ldappcng.xml and ldappc-resolver.xml. Could you reply
>> with sanitized versions, please ?
>>
>
>
>
>
>
>
>