Diego,
You and I have the same issue. UID and CN are not in the schema they
are compiled into LDAP some how, so there is no way to apply an
ordering rule. I can not find if this is possible, or what is involved
in making it happen.
As you can see uid is commented in the schema file as is cn
#attributetype ( 0.9.2342.19200300.100.1.1
# NAME ( 'uid' 'userid' )
# DESC 'RFC1274: user identifier'
# EQUALITY caseIgnoreMatch
# SUBSTR caseIgnoreSubstringsMatch
# SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{256} )
In the past this was possible, or the attributes had an ordering. I do
not know when this changed.
On Fri, Jan 15, 2010 at 8:27 AM, Diego Lima <[email protected]> wrote:
> Hello,
> I have enabled the server-side sorting overlay and I received the following
> error on a search:
> sssvlv: no ordering rule specified and no default ordering rule for
> attribute uid
> <= get_ctrls: n=1 rc=18 err="serverSort control: No ordering rule"
> send_ldap_result: conn=1000 op=7 p=3
> send_ldap_response: msgid=8 tag=101 err=18
> ber_flush2: 50 bytes to sd 13
> ldap_write: want=50, written=50
> 0000: 30 30 02 01 08 65 2b 0a 01 12 04 00 04 24 73 65 00...e+......$se
>
> 0010: 72 76 65 72 53 6f 72 74 20 63 6f 6e 74 72 6f 6c rverSort control
>
> 0020: 3a 20 4e 6f 20 6f 72 64 65 72 69 6e 67 20 72 75 : No ordering ru
>
> 0030: 6c 65 le
>
> conn=1000 op=7 do_search: get_ctrls failed
> Where should I specify the ordering rule for the uid attribute? The core
> schema?
> Thank you
> --
> Diego Lima
>
