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

Why is the difference of "objectclass: organization" and "objectclass: domain"?

I usually add a "objectclass: top" for structural compliance, at least
for Top level definitions.

I have observed that on Solaris9/8 boxes, I have to use "objectclass:
domain" and add also "nisDomain: ..." (for Solaris compatibility?),
whereas on RedHat Linux, I have to use "objectclass: organization".

dn: dc=example,dc=com
objectclass: top
# For RedHat use the next line
#objectclass: organization
# For Solaris use the next line
objectclass: domain
objectClass: nisDomainObject
nisDomain: example.com
objectclass: dcObject
o: Example Companies
dc: example

Anyone bother to explain why it is so? Why is the difference of
"objectclass: organization" and "objectclass: domain"?

I hope this is OpenLDAP related.


-----Original Message-----
From: owner-openldap-software@OpenLDAP.org
[mailto:owner-openldap-software@OpenLDAP.org] On Behalf Of Dave Horsfall
Sent: Wednesday, November 24, 2004 8:04 AM
To: OpenLDAP Software List
Subject: Re: Newbie needs help!

On Tue, 23 Nov 2004, Patrick Ouellet wrote:

> I can't quite get it... as I always having the same error message!

The one you didn't try was:

dn: dc=mit,dc=homelinux,dc=org
objectclass: dcObject
objectclass: organization
o: some
dc: mit		<------------------

And I think you also need "objectclass: top" as well, and possibly some
others such as "objectclass: domain" (sorry to sound so vague, but I'm
not currently in LDAP-mode right now).

Dave Horsfall  DTM  VK2KFU  daveh@ci.com.au  Ph: +61 2 8425-5508 (d)
-5500 (sw) Corinthian Engineering, Level 1, 401 Pacific Hwy, Artarmon,
NSW 2064, Australia