[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Using distingushed name components as attributes.
- To: Stuart Schmukler <Stuart.Schmukler@ncal.kaiperm.org>
- Subject: Re: Using distingushed name components as attributes.
- From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
- Date: Wed, 28 Oct 1998 02:57:06 +0100 (MET)
- Cc: openldap-general@openldap.org
- In-reply-to: <"068CC363666F3046*/c=us/admd= /prmd=kaiperm/o=ncal/ou=notes/s=Schmukler/g=Stuart/"@MHS>
- References: <"068CC363666F3046*/c=us/admd= /prmd=kaiperm/o=ncal/ou=notes/s=Schmukler/g=Stuart/"@MHS>
> I may be very dense here, but I loss in LDAP and X.500 naming land.
> Does a name component attribute have to exist in the LDAP entry in
> addition to being in the DN of the entry?
The RDN component(s), yes. The components naming parent objects, no.
> dn: resourceid=0001, role=md, unit=4b, department=medicine, facility=Mountain View, divison=CA
> objectclass: top
> objectclass: mednode
> resourceid=0001
> role=md
> unit=4b
> department=medicine
> facility=Mountain View
> divison=CA
> telephonenumber: +1 510 267 5491
> ...
Keep the `resourceid:' line. Delete role, unit, department, facility,
division.
> Any pointers to information would help.
rfc2251.
--
Hallvard