Full_Name: John Borwick Version: 2.2.13 OS: Red Hat Workstation 3 URL: Submission from: (NULL) (152.17.54.174) Hello! OpenLDAP advertises the pagedResults control, but back-ldap does not support it. It would be really neat if back-ldap supported pagedResults. Perhaps back-ldap could support pagedResults only if the directory to which back-ldap is pointing supports pagedResults. Also, it would be nice to have a way to turn off the advertisement of a control. Our Outlook 2003 users could not access LDAP for a while, because Outlook detected that OpenLDAP supports pagedResults, but back-ldap does not support pagedResults. Thanks!
changed notes changed state Open to Test moved from Incoming to Software Bugs
On Fri, 13 Aug 2004 borwicjh@wfu.edu wrote: > Full_Name: John Borwick > Version: 2.2.13 > OS: Red Hat Workstation 3 > URL: > Submission from: (NULL) (152.17.54.174) > > > Hello! > > OpenLDAP advertises the pagedResults control, but back-ldap does not support > it. > > It would be really neat if back-ldap supported pagedResults. Perhaps back-ldap > could support pagedResults only if the directory to which back-ldap is pointing > supports pagedResults. > > Also, it would be nice to have a way to turn off the advertisement of a > control. > > Our Outlook 2003 users could not access LDAP for a while, because Outlook > detected that OpenLDAP supports pagedResults, but back-ldap does not support > pagedResults. We've been unable to get Outlook to work properly with 2.2.13 and were forced to fall back to 2.1.30 due to this issue. Unfortunately, 2.2.13 has worked much better for us. Is there some workaround or a fix in the works? -- Marc Wallman Senior Systems Administrator Information Technology Services North Dakota State University Marc.Wallman@ndsu.nodak.edu (701) 231-7168
openldapmarcw@rutabaga.cc.ndsu.nodak.edu wrote: >On Fri, 13 Aug 2004 borwicjh@wfu.edu wrote: > > > >>Full_Name: John Borwick >>Version: 2.2.13 >>OS: Red Hat Workstation 3 >>URL: >>Submission from: (NULL) (152.17.54.174) >> >> >>Hello! >> >>OpenLDAP advertises the pagedResults control, but back-ldap does not support >>it. >> >>It would be really neat if back-ldap supported pagedResults. Perhaps back-ldap >>could support pagedResults only if the directory to which back-ldap is pointing >>supports pagedResults. >> >>Also, it would be nice to have a way to turn off the advertisement of a >>control. >> >>Our Outlook 2003 users could not access LDAP for a while, because Outlook >>detected that OpenLDAP supports pagedResults, but back-ldap does not support >>pagedResults. >> >> > >We've been unable to get Outlook to work properly with 2.2.13 >and were forced to fall back to 2.1.30 due to this issue. >Unfortunately, 2.2.13 has worked much better for us. > >Is there some workaround or a fix in the works? > > I've just committed a fix to HEAD code that enables pagedResults control for back-ldap. If you test it, and report positively, I can prepare a port to 2.2. I do not foresee a release any close, but the fix is (almost) trivial and a patch should be easy to generate. p. SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497
Marc Wallman wrote: > On Fri, 13 Aug 2004 borwicjh@wfu.edu wrote: > > >>Full_Name: John Borwick >>Version: 2.2.13 >>OS: Red Hat Workstation 3 >>URL: >>Submission from: (NULL) (152.17.54.174) >> >> >>Hello! >> >>OpenLDAP advertises the pagedResults control, but back-ldap does not support >>it. >> >>It would be really neat if back-ldap supported pagedResults. Perhaps back-ldap >>could support pagedResults only if the directory to which back-ldap is pointing >>supports pagedResults. >> >>Also, it would be nice to have a way to turn off the advertisement of a >>control. >> >>Our Outlook 2003 users could not access LDAP for a while, because Outlook >>detected that OpenLDAP supports pagedResults, but back-ldap does not support >>pagedResults. > > > We've been unable to get Outlook to work properly with 2.2.13 > and were forced to fall back to 2.1.30 due to this issue. > Unfortunately, 2.2.13 has worked much better for us. > > Is there some workaround or a fix in the works? See http://www.openldap.org/lists/openldap-software/200408/msg00303.html for a source patch, or Pierangelo's suggestion at http://www.openldap.org/lists/openldap-software/200408/msg00321.html . Yours, John -- John Borwick System Administrator Wake Forest University | web http://www.wfu.edu/~borwicjh Winston-Salem, NC, USA | GPG key ID 0x797326D5
changed notes
At 08:41 PM 8/12/2004, borwicjh@wfu.edu wrote: >Full_Name: John Borwick >Version: 2.2.13 >OS: Red Hat Workstation 3 >URL: >Submission from: (NULL) (152.17.54.174) > > >Hello! > >OpenLDAP advertises the pagedResults control, but back-ldap does not support >it. Note that advertisement implies on that the server (as a whole) recognizes (implements) the control. It does not imply that any particular operation which makes use of that control is serviceable. There seems to a bug in OpenLDAP in that it is returning unavailableCriticalExtension for a recognized control used in an appropriate manner. Instead a service error (such as unwillingToPerform) should be returned. >It would be really neat if back-ldap supported pagedResults. Perhaps back-ldap >could support pagedResults only if the directory to which back-ldap is pointing >supports pagedResults. > >Also, it would be nice to have a way to turn off the advertisement of a >control. > >Our Outlook 2003 users could not access LDAP for a while, because Outlook >detected that OpenLDAP supports pagedResults, but back-ldap does not support >pagedResults. > >Thanks!
moved from Software Bugs to Software Enhancements
changed notes changed state Test to Closed
moved from Software Enhancements to Archive.Software Enhancements
back-ldap support applied to HEAD; please test. Also see ITS#3308.