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

Re: ldapadd: Naming violation & alias

>> 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 ) 

This is actually the solution intended by the designers of X.500.
Another (LDAP-centric) alternative is to use the extensibleObject
class.  And another is to use a DIT content rule.  (Note: these
are the same basic alternatives which can be used with 'referral'
objects).

Kurt