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

openLDAP paged response problem



Hi,

 

I’m using OpenLDAP backend with .NET 2.0 System.DirectoryServices.Protocols API in my application. I’m trying to issue PagedResult control as part of my request to get results in multiple pages that code can navigate. This would use rfc2696 which is already supported in OpenLDAP. But when I run my code it comes back with exception that ‘'critical control unavailable in context’.

 

 

I’ve attached the capture from OpenLDAP server

##

T 10.218.5.27:33236 -> 10.217.94.154:389 [AP]

  0........c....s.!dc=openldap,dc=dev,dc=net6,dc=com.......................objectClass..person0.... ..distinguishedName..sn..manager...../0....)..1.2.840.1

  13556.1.4.319.....0...........

#

T 10.217.94.154:389 -> 10.218.5.27:33236 [AP]

  03...e...5...'critical control unavailable in context

#

 

But OpenLDAP does support the control 1.2.840.113556.1.4.319 as listed in my query response against rootDSE below

 

DB2-95-02:~ # ldapsearch -x -h 10.217.94.154 -b "" -s base '(objectclass=*)' +

# extended LDIF

#

# LDAPv3

# base <> with scope baseObject

# filter: (objectclass=*)

# requesting: +

#

 

#

dn:

structuralObjectClass: OpenLDAProotDSE

configContext: cn=config

namingContexts: dc=openldap,dc=dev,dc=net6,dc=com

supportedControl: 1.3.6.1.4.1.4203.1.9.1.1

supportedControl: 2.16.840.1.113730.3.4.18

supportedControl: 2.16.840.1.113730.3.4.2

supportedControl: 1.3.6.1.4.1.4203.1.10.1

supportedControl: 1.2.840.113556.1.4.319

supportedControl: 1.2.826.0.1.334810.2.3

supportedControl: 1.3.6.1.1.13.2

supportedControl: 1.3.6.1.1.13.1

supportedControl: 1.3.6.1.1.12

supportedExtension: 1.3.6.1.4.1.4203.1.11.1

supportedExtension: 1.3.6.1.4.1.4203.1.11.3

supportedFeatures: 1.3.6.1.1.14

supportedFeatures: 1.3.6.1.4.1.4203.1.5.1

supportedFeatures: 1.3.6.1.4.1.4203.1.5.2

supportedFeatures: 1.3.6.1.4.1.4203.1.5.3

supportedFeatures: 1.3.6.1.4.1.4203.1.5.4

supportedFeatures: 1.3.6.1.4.1.4203.1.5.5

supportedLDAPVersion: 3

entryDN:

subschemaSubentry: cn=Subschema

 

 

Any idea why the server responds with ‘'critical control unavailable in context’ message? I’m using OpenLDAP v 2.3.19

 

[root@labvmware ~]# slapd -V

@(#) $OpenLDAP: slapd 2.3.19 (Feb 13 2006 11:19:24) $

        root@ls20-bc1-14.build.redhat.com:/usr/src/build/708086-i386/BUILD/openldap-2.3.19/openldap-2.3.19/build-servers/servers/slapd

 

Thanks,

Navaneetha