--On Saturday, November 17, 2018 11:27 AM +0000 michael(a)stroeder.com wrote:
With such a layout the standard schema shipped with the software is
part of cn=config but can still be dynamically changed (by directly
modifying subschema subentry). But there's always a way out of trouble
because you can manually fix the separate LDIF schema file(s).
You can manually fix the ones stored in cn=config with OpenLDAP now, and
you can also change it dynamically. I'm not sure how either of those
statements address the problem discussed in this ITS.
Quite frankly, I wrote a tool to automatically update the schema stored
with cn=config so that it matched whatever was shipped in a given release
on upgrade when I worked @ Zimbra:
I.e., I don't really see what in the above is different from what you can
do now, nor do I see how it resolves the issue of a binary compiled file
that must have references to valid schema compiled into it.
Packaged, certified, and supported LDAP solutions powered by OpenLDAP: