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

Re: [Models] alias object class



>From Kathy's and your reply, I gather one couldnt use alias object class
diretcly but would need to have some subclass of it.
The example id [Models] is:
Example:
      dn: cn=bar,dc=example,dc=com
      objectClass: top
      objectClass: alias
      objectClass: extensibleObject
      cn: bar
      aliasedObjectName: cn=foo,dc=example,dc=com

That seems incorrect because extensibleObject is an AUX class.
Comments ?

Prasad

>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 8/14/2004 1:43:34 PM >>>
At 05:31 PM 8/13/2004, Vithalprasad Gaitonde wrote:

>An entry with the 'alias' object class must also belong to an object
>  class (or classes), or be governed by a DIT content rule, which
>allows
>  suitable naming attributes to be present.
>
>Since alias is a structural class, an entry belonging to this class
can
>belong to only other auxilliary classes not other sturctural classes.

The entry can be of a subclass of 'alias' (and hence
belong to 'alias' as well).  

>Auxilliary classes cannot have nameforms. Thus the question of what
>naimg attribute to use for an  entry which is an alias is not
>indeterminate.
>
>Comments?
>
>Prasad