[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: OpenLDAP advertises pagedResults but LDAP backend doesn't support it [was Re: Outlook 2003 "unavailable critical extension"]

John Borwick wrote:

OK.  We have looked into our Outlook problem.

Outlook queries dn="" for the supportedControls.  It receives
"1.2.840.113556.1.4.319" (pagedResults).  Outlook then queries
"o=WFU,c=US" for the user.

o=WFU,c=US is our LDAP backend.  It does not support pagedResults.

dc=wfu,dc=edu is our bdb backend.  It supports pagedResults.

We do not have the ability to make users use "dc=wfu,dc=edu".


1. Is it possible to make openLDAP *not* advertised pagedResults in the
list of supportedControls?  I tried

access to dn.exact="" filter="(supportedControl=1.2.840.113556.1.4.319)"
by * none

access to dn.exact="" attrs=supportedControl val=1.2.840.113556.1.4.319
   by * none

should do the trick; another solution is hack servers/slapd/back-ldap/init.c
and eliminate the control from the supported controls list.

at the very beginning of the ruleset, but that doesn't seem to work.

2. Is the LDAP backend going to support pagedResults?

I'll look at it; in principle, it should, by propagating both the control request and the response back and forth from the client to the remote server.


   SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497