An application is receiving unsupported critical extensions from LDAP. It is trying to use extension "1.2.840.113556.1.4.319", which is noticed is also used by the Solaris Naming client. When I check to see if the extension is supported, it doesn't appear on the list

ldapsearch -h sun79 -p 3890 -b "" -s base 'objectclass=*'

objectClass=top
namingContexts=cn=changelog
namingContexts=o=NetscapeRoot
namingContexts=o=pseg.com,c=US
supportedExtension=2.16.840.1.113730.3.5.7
supportedExtension=2.16.840.1.113730.3.5.8
supportedExtension=2.16.840.1.113730.3.5.3
supportedExtension=2.16.840.1.113730.3.5.5
supportedExtension=2.16.840.1.113730.3.5.6
supportedExtension=2.16.840.1.113730.3.5.4
supportedExtension=1.3.6.1.4.1.42.2.27.9.6.1
supportedExtension=1.3.6.1.4.1.42.2.27.9.6.2
supportedExtension=1.3.6.1.4.1.42.2.27.9.6.3
supportedExtension=1.3.6.1.4.1.42.2.27.9.6.4
supportedExtension=1.3.6.1.4.1.42.2.27.9.6.5
supportedExtension=1.3.6.1.4.1.42.2.27.9.6.6
supportedExtension=1.3.6.1.4.1.42.2.27.9.6.7
supportedExtension=1.3.6.1.4.1.42.2.27.9.6.8
supportedExtension=1.3.6.1.4.1.42.2.27.9.6.9
supportedExtension=1.3.6.1.4.1.42.2.27.9.6.11
supportedExtension=1.3.6.1.4.1.42.2.27.9.6.12
supportedExtension=1.3.6.1.4.1.42.2.27.9.6.13
supportedExtension=1.3.6.1.4.1.42.2.27.9.6.14
supportedExtension=1.3.6.1.4.1.42.2.27.9.6.15
supportedExtension=1.3.6.1.4.1.42.2.27.9.6.16
supportedExtension=1.3.6.1.4.1.42.2.27.9.6.17
supportedExtension=1.3.6.1.4.1.42.2.27.9.6.18
supportedExtension=1.3.6.1.4.1.42.2.27.9.6.19
supportedExtension=1.3.6.1.4.1.42.2.27.9.6.21
supportedExtension=1.3.6.1.4.1.42.2.27.9.6.22
supportedExtension=1.3.6.1.4.1.4203.1.11.3
supportedControl=2.16.840.1.113730.3.4.2
supportedControl=2.16.840.1.113730.3.4.3
supportedControl=2.16.840.1.113730.3.4.4
supportedControl=2.16.840.1.113730.3.4.5
supportedControl=1.2.840.113556.1.4.473
supportedControl=2.16.840.1.113730.3.4.9
supportedControl=2.16.840.1.113730.3.4.16
supportedControl=2.16.840.1.113730.3.4.15
supportedControl=2.16.840.1.113730.3.4.17
supportedControl=2.16.840.1.113730.3.4.19
supportedControl=1.3.6.1.4.1.42.2.27.9.5.2
supportedControl=1.3.6.1.4.1.42.2.27.9.5.6
supportedControl=1.3.6.1.4.1.42.2.27.9.5.8
supportedControl=2.16.840.1.113730.3.4.14
supportedControl=1.3.6.1.4.1.1466.29539.12
supportedControl=1.3.6.1.4.1.42.2.27.9.5.4
supportedControl=2.16.840.1.113730.3.4.12
supportedControl=2.16.840.1.113730.3.4.18
supportedControl=2.16.840.1.113730.3.4.13
supportedSASLMechanisms=EXTERNAL
supportedSASLMechanisms=GSSAPI
supportedSASLMechanisms=DIGEST-MD5
supportedLDAPVersion=2
supportedLDAPVersion=3
vendorName=Sun Microsystems, Inc.
vendorVersion=Sun Java(TM) System Directory Server/5.2_Patch_4
dataversion=020070920113115020070920113115020070920113115
netscapemdsuffix=cn=ldap://dc=sun79,dc=pseg,dc=com:3890
changeLog=cn=changelog
firstchangenumber=1
lastchangenumber=12699157

The documentation tells me to check for it's support, but not how to add it if it's missing. How do I add it?

We are running Sun Java(TM) System Directory Server/5.2_Patch_4 B2005.230.0041 (64-bit) on Solaris 9 (Generic_112233-12 sun4u sparc SUNW,Sun-Fire-480R)

 

 

Simple pages results are not supported in Sun Directory Server 5.x or 6.x.
We have a more powerful mechanism : VLV which allow paging up and down, like a scroll list.

Solaris Naming Client knows how to handle either Simple Page or VLV.

Regards,

Ludovic.

 

 

Then how do I get our LDAP server to respond properly to the application (see their response below)?

{
R&D checked the code and they see that we do use the extension "1.2.840.113556.1.4.319", but it is being used as NOT a critical extension.

That means the LDAP server should ignore this extension and not give an error.
( see http://www3.ietf.org/proceedings/02mar/I-D/draft-ietf-ldapbis-url-01.txt )

For some reason, it seems that the LDAP server at your end thinks that its a critical extension and hence it gives the ?unsupported critical extension" error.

Please ask your LDAP admin why this particular behavior is shown by the LDAP.
}

 

 

If the control is truely mark as non critical, the server will ignore it and reply to the request.
If the server returns the error "unsupported critical extension" it means the control is stated as critical. There is no code in our server detecting the Simple Page Control and rejecting it (regardless of the criticality).

Regards,

Ludovic.

 

 

Hi Ludovic,

Can you tell me why Sun is bypassing RFC 2696 which is support for "simple paged results"? When I configure paging, I get an "unsupported critical extension" from SUN. Is VLV/scrolling Sun's replacing for paging and how does that adhere to the rfc?

Thanks.

 

 

Please disregard my previous post. I've reread the RFC 2696 and interpreted the following:

The RFC references the guidelines for the ldap client that is using the page control. There is some references as to what the server MUST do (return unsupportedCriticalExtension error when the situation suits) but no where does the RFC indicate that support for paging is a requirement for ldapv3.

Thank you.