Got it! Very helpful! Thank you!
Hmm... so would you recommend removing the replication of cn=config for now? Individually adding the schema to each master is feasible for us.
If it's not required then yes, I personally would not use it at this time. For example, ITS#8286, although it only discusses a single matching rule, ended up touching numerous files, and it's directly related to using cn=config and cn=config replication (<
https://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commitdiff;h
=3add82a3bb30b94afd23ff5e2c00c59ca8a931d8>).
To which I should add -- And is only being fixed for OpenLDAP 2.5 and later.
...2.5....any ETA on that? ;)
Best, dave
--On Wednesday, April 03, 2019 5:27 PM -0400 Dave Macias davama@gmail.com wrote:
To which I should add -- And is only being fixed for OpenLDAP 2.5 and later.
...2.5....any ETA on that? ;)
"When it's ready"? ;)
We've been reviewing our development process and are waiting on a writeup from a project member on a new approach going forward to be debated by the project team and then implemented as our process for 2.5 and future.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
openldap-technical@openldap.org
-
Dave Macias -
Quanah Gibson-Mount