[LDAP-interop] eDirectory and nesting of OCs

[Peter Schober]

hi folks,

on a public mailing list list about the groupware software
"open-xchange" (shortend to OX) came up this discussion about "nesting"
objects of certain objectclasses.
open-xchange, like many others, currently makes use of 'ou's below
e.g. 'inetOrgPerson's e.g. for storing personal contacts "below" the
person owning them. now people claim you cannot do this with Novell
eDirectory (nesting of arbitrary objectclasses). see the quote below.

any info or opinion on that matter?
does it make sense to bend everything in eDir's direction?
does anyone have information on what's the deal with eDir in that
regard? I would expect software that raises arbitrary limits on my DIT
design to at least be configureable in that regard?

thanks for any pointers.

regards,
-p.schober

ps: I sent this to the ldap at umich list, but this was over 36 hours ago and
still no sign of it. *sigh*   will this list *ever* work? not that having a
working mailing list manager would be rocket sience, these days...

----- Forwarded message -----
Subject: Re: [OX General] Novell Edirectory

Peter Schober schrieb:
> * Marcus Klein <> [2005-08-25 11:29]:
> 
>>Patricio Bruna V schrieb:
>>
>>>has anyone get OX works with eDirectory? 
>>>are any howto?
>>
>> This doesn't work currently because OX uses some strange object
>>hierarchies in LDAP that will never work in eDirectory. Best example
>>of this strangeness is an object with class organization as a
>>subobject of the class organizationalUnit.  This doesn't makes any
>>sense but openLDAP doesn't complain about this problems.  So some
>>rework has to be done here.
> 
> 
> could you point me to the relevant LDAP (or X.500) standards where it
> says you can't have organizations below organizationalUnits?

I don't know about a standard that forbids organizations below
organizationalUnits. But eDirectory stores in its schema in which container
classes an object of a certain class can be created. The classes organization
and organizationalUnit already exist in the standard schema and you have to
delete the organization class and recreate it with organizationalUnit as a
possible container class. These both classes are only one example. OX uses
organizationalUnits below inetOrgPersons/OXUserObjects for the personal
addressbook, which is also not allowed in standard schema of eDirectory.

So what do you propose to deal with these problems?

> thanks,
> -p.schober

Best regards,

Marcus Klein
----- End forwarded message -----
_______________________________________________
LDAP-interop mailing list
LDAP-interop at fini.net
http://lists.fini.net/mailman/listinfo/ldap-interop