Limitations to the LDAP Data Cache

The LDAP data cache does not provide for:

• Reading the cache for searches where a list of entries is expected, for example, searching for attendees for a meeting. This type of search is subject to any LDAP delay. For instance, a newly created calendar will not appear in a calendar search if the LDAP search option is active and the search is performed within the delay period following the creation of a new calendar.

• Reading and writing of the cache across multiple front-end servers. Each front-end server has its own cache, which is not aware of data in other caches.

• The capability to handle a user who doesn’t always log into the same server. Such a user will generate different LDAP data in the cache on each server.