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

slapo-allowed: allowedChildClasses and allowedChildClassesEffective (was: Seg faults with 2.4.22)

To: masarati@aero.polimi.it
Subject: slapo-allowed: allowedChildClasses and allowedChildClassesEffective (was: Seg faults with 2.4.22)
From: Michael Ströder <michael@stroeder.com>
Date: Tue, 27 Apr 2010 20:10:03 +0200
Cc: openldap-devel@OpenLDAP.org
In-reply-to: <dbbe86527e717bdeb967aa409a697459.squirrel@www.aero.polimi.it>
References: <4BD6F8E5.6000800@stroeder.com> <dbbe86527e717bdeb967aa409a697459.squirrel@www.aero.polimi.it>
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 SeaMonkey/2.0.4

Redirected this to openldap-devel...

masarati@aero.polimi.it wrote:
> slapo-allowed was modified between 2.4.21 and 2.4.22; support for
> allowedChildClasses and allowedChildClassesEffective was added.

The semantics you've implemented seems to be incompatible with my
implementation in web2ldap which works correctly with MS AD. I do not claim to
know the *exact* semantics of these attributes though.

web2ldap only uses the attribute 'allowedChildClasses'.
In the object class select form web2ldap now only shows an empty list of
STRUCTURAL object classes to be usable for a new entry. AUXILIARY object
classes are shown. At first glance it seems STRUCTURAL object classes are not
returned by slapo-allowed in the search result at all.

Ciao, Michael.

Follow-Ups:
- Re: slapo-allowed: allowedChildClasses and allowedChildClassesEffective (was: Seg faults with 2.4.22)
  - From: masarati@aero.polimi.it

Prev by Date: Re: RE24 call for testing (round 1)
Next by Date: Re: slapo-allowed: allowedChildClasses and allowedChildClassesEffective (was: Seg faults with 2.4.22)
Index(es):
- Chronological
- Thread