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

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

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

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

2. Is the LDAP backend going to support pagedResults?

Thank you very much!


            John Borwick      | work                 336 758 2507
        Systems Administrator | cell                 336 391 6623
       Wake Forest University | web  http://www.wfu.edu/~borwicjh
       Winston-Salem, NC, USA | GPG key ID               56D60872

Attachment: signature.asc
Description: OpenPGP digital signature