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

Can ldap backend strip paged result critial extension?

To: "'openldap-software@openldap.org'" <openldap-software@openldap.org>
Subject: Can ldap backend strip paged result critial extension?
From: "Loving, Kent" <kent.loving@boeing.com>
Date: Mon, 1 Feb 2010 09:15:41 -0800
Accept-language: en-US
Acceptlanguage: en-US
Content-language: en-US
In-reply-to: <26EE928383B71944A4A60630368EBABC057F93BA86@XCH-NW-08V.nw.nos.boeing.com>
References: <26EE928383B71944A4A60630368EBABC057F93BA86@XCH-NW-08V.nw.nos.boeing.com>
Thread-index: AcqgsaITAInR/mAmRiKRThZQ/afkWwCsIBXQ
Thread-topic: Can ldap backend strip paged result critial extension?

I am trying to install an application that sets the paged result extension as critical in all its searches. I tried to connect this application to an existing LDAP server which does not support that extension and I get error=12, Critical extension is unavailable.

I am not able to modify the settings of the application nor the existing LDAP server.

I thought to try OpenLDAP as a proxy between the app and the existing server. I installed OpenLDAP 2.4 and added database of type ldap, with suffix and uri for the existing LDAP server. Searches work great using ldapsearch (data is retrieved from the existing server) but searches from the application still return error 12.

Is there any way I can instruct the ldap backend to strip the paged result request to the existing server, yet still have the OpenLDAP proxy honor the app's request?

Kent Loving

Follow-Ups:
- Re: Can ldap backend strip paged result critial extension?
  - From: Howard Chu <hyc@symas.com>

Prev by Date: TLS Replication on Ubuntu 9.04
Next by Date: Replication problem using synrepl with TLS (Starttls)
Index(es):
- Chronological
- Thread