[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openldap-technical
Subject:    Re: changing objectClass in 2.4
From:       Mattes <r.mattes () mh-freiburg ! de>
Date:       2015-03-25 13:13:41
Message-ID: 4f80-5512b480-c3-1b73f20 () 19368890
[Download RAW message or body]


 
Am Mittwoch, 25. März 2015 13:34 CET, Michael Ströder <michael(a)stroeder.com> schrieb: 
 
> Igor Shmukler wrote:
> > I would like to change the objectClass for an existing record -
> > specifically I want to replace dcObject for a custom one, so instead
> > of:
> > objectClass: top
> > objectClass: dcObject
> > objectClass: organization
> >
> > I would have:
> > objectClass: top
> > objectClass: myDcObject
> > objectClass: organization
> 
> Did you try? If yes, what's the problem?
> 
> > I found a thread where Kurt mentions that back in day, there was
> > planned support for 2.4 to offer such functionality. [
> > http://www.openldap.org/lists/openldap-software/200604/msg00074.html ]
> > Was this done? It is working now?
> 
> The above posting was solely about modifying the structural object class of an 
> entry (which is forbidden).
> 
> You can change auxiliary object classes at any time after entry creation. Of 
> course you have to take care about changed attribute sets - especially the 
> ones listed as MUST.

... and the atrribute used as the RDN (unless that attribute is present in both the
old and the new oject class' MAY).

 Cheers, RalfD

>  So if myDcObject is an auxiliary object class it's not a 
> problem at all.
> 
> Ciao, Michael.
> 
 
 
 
 





[prev in list] [next in list] [prev in thread] [next in thread]