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

Re: disable simple paged results control support?!

To: Igor Shmukler <igor.shmukler@gmail.com>
Subject: Re: disable simple paged results control support?!
From: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
Date: Wed, 2 Sep 2015 11:23:33 +0100
Cc: "openldap-technical@openldap.org" <openldap-technical@openldap.org>
Content-disposition: inline
In-reply-to: <CAA1SNA0mqK6CR+ensno1Qz+uAifijCGs7y3WN6rpsTx1b2k6=A@mail.gmail.com>
References: <CAA1SNA0mqK6CR+ensno1Qz+uAifijCGs7y3WN6rpsTx1b2k6=A@mail.gmail.com>
User-agent: Mutt/1.5.21 (2010-09-15)

On Thu, Aug 27, 2015 at 01:46:53PM +0300, Igor Shmukler wrote:

> Is it possible to disable OpenLDAP server-side support of simple paged
> results control, so the OpenLDAP server would respond that this
> control is unavailable?
> 
> I don't have an LDAP proxy, nor ODSEE configured. OpenLDAP saved me
> many times, in past. Can OpenLDAP be configured to do what I need, so
> I could test my fallback code in the client using an OpenLDAP server?

Have a look at the RETCODE overlay: slapo-retcode(5) - this should allow you
to return whatever error codes you like to your client during testing.

Andrew
-- 
-----------------------------------------------------------------------
|                 From Andrew Findlay, Skills 1st Ltd                 |
| Consultant in large-scale systems, networks, and directory services |
|     http://www.skills-1st.co.uk/                +44 1628 782565     |
-----------------------------------------------------------------------

Prev by Date: Re: load balancer
Next by Date: Re: "olcSizeLimit: size.prtotal=disabled" ignored?
Index(es):
- Chronological
- Thread