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

Re: ldap_add: Naming violation (64)

To: King Lung Chiu <csklc@farrer.hpc.csiro.au>
Subject: Re: ldap_add: Naming violation (64)
From: Quanah Gibson-Mount <quanah@stanford.edu>
Date: Thu, 26 Feb 2004 22:50:12 -0800
Cc: OpenLDAP software List <openldap-software@OpenLDAP.org>
Content-disposition: inline
In-reply-to: <Pine.LNX.4.44.0402271727320.11603-100000@farrer.hpc.csiro.au>
References: <Pine.LNX.4.44.0402271727320.11603-100000@farrer.hpc.csiro.au>

--On Friday, February 27, 2004 5:40 PM +1100 King Lung Chiu <csklc@farrer.hpc.csiro.au> wrote:

Hi Quanah,

thanks for the reply,
Does that mean my dn shouldn't have been "dc=hpc,dc=csiro,dc=au"?

How do  I decide what format to use for a dn? (eg. quickstart example
from  openldap's site used "dn: dc=example,dc=com", whereas your post
above  seems to suggest it should be "dn: ou=example,dc=com")

It depends entirely on what you are doing. If hpc is an organizational unit, you should use ou. It would probably help to do some reading on schema's and LDAP schema design.

--Quanah

--
Quanah Gibson-Mount
Principal Software Developer
ITSS/TSS/Computing Systems
ITSS/TSS/Infrastructure Operations
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html

References:
- Re: ldap_add: Naming violation (64)
  - From: King Lung Chiu <csklc@farrer.hpc.csiro.au>

Prev by Date: RE: ldap_add: Naming violation (64)
Next by Date: Re: ldap_add: Naming violation (64)
Index(es):
- Chronological
- Thread