caching search results ?

[Tom Zeller]

I'm looking for advice regarding vt-ldap and caching searches.

For example, with Grouper we are provisioning memberships of the form :

dn: cn=groupA, ou=groups
member: cn=memberA

dn: cn=groupB, ou=groups
member: cn=memberA

dn: cn=memberA,ou=people
cn=memberA

We populate the member attribute via an ldap search returning a DN,
e.g. "(cn=memberA)". It would be nice if we could define a session,
perhaps based on time (TTL) or via a method call (e.g. session.start()
and session.end()), during which the results of search operations are
cached to avoid redundant lookups (e.g. we search once for
(cn=memberA) when provisioning groupA and a second time for groupB).

Previously, we've cached in java using maps, where keys are search
filters and values are DNs, but I was looking for something
configurable via xml or properties files. Perhaps a caching layer
(ehcache) is the answer, but I thought I would ask.

Thanks!
Tom

[Daniel Fisher]

ehcache is probably your best bet right now.
I'll file a feature request for this, it's probably something that could be done for version 4.

--Daniel