[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: which naming attribute ...
I believe it is as Steven says. In particular, aliasedObjectName is a DN an
not realy suitable for use as an RDN!
Ron.
-----Original Message-----
From: Volpers, Helmut [mailto:helmut.volpers@icn.siemens.de]
Sent: Wednesday, 11 October 2000 18:06
To: 'steven.legg@adacel.com.au'; 'sanjay jain'; 'ldapext'
Subject: RE: which naming attribute ...
Hi
I think Bruce gives the correct definition.
> -----Original Message-----
> From: Steven Legg [mailto:steven.legg@adacel.com.au]
> Sent: Mittwoch, 11. Oktober 2000 04:12
> To: 'sanjay jain'; 'ldapext'
> Subject: RE: which naming attribute ...
>
>
>
> Sanjay,
>
> Any desired naming attribute could be introduced by:
>
> (1) subclassing the alias object class,
why do want subclassing of aliases ?
do you want to give an alias additional attributes (e.g. TN or e-mail
address ?)
> (2) defining an auxiliary object class with the naming attribute and
> adding the auxiliary class to the alias entry, or
> (3) putting the naming attribute in a DIT content rule for the alias
> object class.
>
> I lean towards (1).
>
> I think there might be implementations that require the
> naming attribute
> type of the alias to be the same as the aliased entry's
> naming attribute.
But this is nowhere described in the standards ?
Helmut
> You might want to conform to that.
>
> Regards,
> Steven
>
> -----Original Message-----
> From: sanjay jain [mailto:sanjay.jain@software.com]
> Sent: Wednesday, 11 October 2000 11:49
> To: ldapext
> Subject: which naming attribute ...
>
>
> which naming attribute can be used to create alias objects ?
> thanks
>