[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: (ITS#9020) Inconsistent cn=config objectClasses for overlays
On Thu, May 09, 2019 at 04:21:56PM +0000, quanah@openldap.org wrote:
> The majority of supported overlays use an objectClass of the format:
>
> olcOVERLAYConfig
>
> However, there are two overlays that do *not* follow this format, which is
> confusing.
>
> memberOf -> olcMemberOf
> dynlist -> olcDynamicList
>
> For 2.5, I would suggest we change these to be consistent with all the other
> overlays and document this change in the Admin Guide section on upgrade notes
> etc.
Maybe we could change the name in 2.4 with the proposed names as the
primary keeping the old one as an alternative? Don't remember if slapcat
would translate them accordingly. If it does, we could just drop the old
name in 2.5 (and have everyone slapcat cn=config with OpenLDAP >= 2.4.48
or wherever this lands).
Or just do the above in 2.5 only.
--
OndÅ?ej KuznÃk
Senior Software Engineer
Symas Corporation http://www.symas.com
Packaged, certified, and supported LDAP solutions powered by OpenLDAP