Re: ldapadd: Naming violation & alias

["Emmanuel.Leguy" <Emmanuel.Leguy@lifl.fr>]

Hello,

I checked the core.schema the code of slapd and the rfc 2256: an alias 
must not contain a cn attribute.
But, as I said, ldapadd complains because he needs a cn attribute.
If I add a cn attribute, ldapadd complains because this attribute (cn) 
is not allowed in aliases.
A dirty solution is to add an ObjectClass like this:

objectclass ( x.x.x.x NAME 'myAlias'
      DESC 'not RFC2256: an alias'
      SUP alias STRUCTURAL
      MUST cn )

or change the alias definition in slapd code:

objectclass ( 2.5.6.1 NAME 'alias'
      DESC 'not RFC2256: an alias'
      SUP top STRUCTURAL
      MUST aliasedObjectName $ cn )

A better solution (so the rfc should be respected) is to pach ldapadd. 
In fact, the function entry_naming_check() in servers/slapd/schema_check.c.

What do you thing? Am I wrong?

Thanx,

Manu.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature