[Date Prev][Date Next]
Server Side sort and the cn attribute
- To: firstname.lastname@example.org
- Subject: Server Side sort and the cn attribute
- From: Edward Capriolo <email@example.com>
- Date: Fri, 11 Dec 2009 13:31:50 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=v7B87yWQ699zhiWLyh+wSQEyklso7jcozAYitJh5Bnw=; b=K338lIon+eftl9f92jxT/559ieDYcTmM0fxMsk4YPAsaryJi9qG9a268teJ/0qkGNR 2z0D/KLWnJdA9SX+UgIDhdEWt568dXWn9wk0BPX3yFkFvFalDlnh3HT3huDG/wPee8Lo U+I9lZUviuVCIDBozEsLpqqwTGKcDhvOnCXbg=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=qaGvpVvRXcY80x/ufD402fh0Gxm5lxQQd/c4sojXOdQ0zwI/ormaBQAzPnNz4KIkRu ZqdF0fWvGGPQ6sLgIzuJlazJ4eUjv/9a7f1i9krJf1k5spksZEAV4VUW7QbyFo4AUf/a bmbQ4WkmE646Naqcz8Xc2XMkeEw+3YQT0mnSc=
We use openldap as a back end for many things. One of the thing, it
can be used for is an address book for outlook. Recently we upgrade to
2.4.16->2.4.20 from 2.(who knows how old).
Outlook 2003 clients stopped working:
So I followed the instructions here to enable server side sorting:
I was able to add the ordering to the sn attribute.
attributetype ( 188.8.131.52 NAME ( 'sn' 'surname' )
DESC 'RFC2256: last (family) name(s) for which the entity is known by'
SUP name )
Unfortunately outlook is looking at the cn attribute
@400000004b21316a0e808064 sssvlv: no ordering rule specified and no
default ordering rule for attribute cn
@400000004b21316a0e808834 <= get_ctrls: n=1 rc=18 err="serverSort
control: No ordering rule"
That unfortunately is not defined in the core.schema
# system schema
#attributetype ( 184.108.40.206 NAME ( 'cn' 'commonName' )
# DESC 'RFC2256: common name(s) for which the entity is known by'
# SUP name )
I am sure there is a good reason why cn does not have an ordering, but
I am guessing it used to have this in the distant past since this
previously worked. So how would I go about changing the system schema?
Or does anyone have a better way to deal with this.
(I know I could play with client registry (kb) article but I would
like to handle this server side)
Thank you for your insights.