Hi Cédric,
Which version of Jahia are you using ? In 4.0.5 we added a lot of caches
in the LDAP implementation, so you shouldn't be seeing this problem anymore.
Cédric REYMANN wrote:
Hi,
I have two problems with the LDAP capabilities of Jahia.
The first one is that Jahia gather all the information from the LDAP
server for each visited page. As if the cache weren't used. By the
way, these LDAP requests are very slow if we compare them to another
LDAP client for which it works fine. What can we do ?
The second point is that when we make a modification to LDAP users or
group, this modification isn't seen by Jahia. This is strange
regarding the first problem. And flushing the LDAP caches isn't
sufficient : after the flush of all caches, it works fine. The
question is, how does the LDAP cache work and is it possible to make
the cache expire sometime ? So that the guy who modify the LDAP
doesn't need to refer to the Jahia administrator.
You can expire the cache manually through the administration ("Server
and cache status"). You could also programmatically expire the cache by
flusing the corresponding cache. For the moment there is no time-based
expiration possible but will be possible in future versions of Jahia (as
we will be making the cache implementation pluggeable).
Regards,
Serge Huber.
