[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Behavior change on overlay sssvlv
- To: "openldap-technical@openldap.org" <openldap-technical@openldap.org>
- Subject: Behavior change on overlay sssvlv
- From: Clément OUDOT <clem.oudot@gmail.com>
- Date: Thu, 19 Apr 2012 09:20:50 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=E6ZFzGB+kZW/pByLbudCpx5Tjnk2qSXXL9+OoV8Sa6g=; b=QLR7Z90GHSVgBBMOQwgRZbaQZqb8KMdlejUkTP6UMdQ5FugPamt9NAEY0a1CJ5zpng Hb53XXDG6nYT6VAAPJ2qvC4Hh4G9fPOOndPltOaum4yFi8QSBvYMwebKMOTRSBORIi1/ I25rLnlmjY972WN9L6HWy1x7oIcs2Tw4eyNjSyewAaUj0HpuBxseb5RmbBwV5ckvHvTo YI5uEJ/dfILoJplwvaEdp0vHfHNx89J4QKOITiG+oUZhl6LLbGLeSLQgvwa5I9Stka+S CmKFJEnPcahDrHb5oiDi21EgShgg/Dmg7jR/EHDSIqwYX3D4/ki3gzk1IxHKUH/02Mv7 25RA==
Hello,
I noticed that with OpenLDAP 2.4.30, a search request with a non
criticical sss control on an attribute without ordering matching rule
returns an error:
clement@ader:~/Programmes/openldap$ bin/ldapsearch -H
ldap://localhost:3389 -D ou=lsc,ou=accounts,ou=XXX -w secret -b
ou=people,ou=XXX -E sss=cn
# extended LDIF
#
# LDAPv3
# with server side sorting control
#
# search result
search: 2
result: 18 Inappropriate matching
text: serverSort control: No ordering rule
# numResponses: 1
Before, the error was only returned if the control was set to
critical. This was discussed in this ITS:
http://www.openldap.org/its/index.cgi/Software%20Bugs?id=6647
Is this behavior change intentional or is this a side effect of of
recent commit?
Clément.