[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Different CN's for DN and CN.

Thanks for clearing that up!

It looks like I have a load of perl-coding so I can clear this up :(

On Mon, 2003-03-17 at 12:07, Jehan PROCACCIA wrote:
> Yes that's a new constraint comming with 2.1.14 and above ...(better 
> respect to RFCs i supose)
> RDN attribute must be exactly the same (except respect of case) as the 
> attributre difined in the object. in your case you must have:
>  > dn: cn=myname, ou=people, dc=sws, dc=oldham, dc=uk, dc=net
>  > cn: myname
> and  NOT:
>  > cn: My Name
> Andrew McCall wrote:
> > Hi,
> > 
> > I have an OpenLDAP directory set up and it all works great. However
> > after explaining it to some other people who know about LDAP they
> > pointed out that I have a "problem" with the way my CN and DN are set
> > up.
> > 
> > Here is how a typical entry would look :
> > 
> > dn: cn=myname, ou=people, dc=sws, dc=oldham, dc=uk, dc=net
> > cn: My Name
> > sn: Primary School
> > ...
> > ... etc.
> > 
> > You will notice that the dn: contains "myname" all one work, all lower
> > case for the cn part of the dn, but the cn: contains My Name, leading
> > cap's with a space for it.
> > 
> > How does this work? Does this make the LDAP "wrong"?
> > 
> > Everything works, but it just makes our naming convention a little
> > difficult to maintain, I am planning on changing the DN to hold the UID
> > rather than the CN, but some entries don't have a UID, so it means that
> > I will have a mixture or DN's with UID's and DN's with CN's.

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.