Re: case sensitivity of dn

["Kurt D. Zeilenga" <Kurt@OpenLDAP.org>]

At 05:31 PM 8/28/00 +0200, Ian Maloney wrote:
>I am trying to add 2 entries to a directory with the following 2 DNs
>(note the slight case difference in p2pPrnName values)
>
>dn: p2pPrnName=MYpr, ou=p2pPrinterQ, ou=Services, o=ubs.com
>dn: p2pPrnName=MyPr, ou=p2pPrinterQ, ou=Services, o=ubs.com
>
>The add of the second entry fails with error=68  (i.e. already exists)
>This is despite the fact that the attribute p2pPrnName is defined as
>Case Exact String (ces) making the two p2pPrnName attribute values
>different.
>
>The question is: Is this result,
>    a) standard (RFC defined) behaviour, i.e. dn can *never* be case
>sensitive ?

no.

>    b) only an implementation issue,

yes.  Some servers place restrictions upon RDN type/value pairs.
Some servers disallow multiple RDN type/value pairs.  Some
servers place other restrictions upon naming.

Many U-Mich derived implementations, including OpenLDAP,
effectively limit DNs to attribute types which have case
insensitive matching.

Kurt