On 11/6/18, Frank Swasey <[email protected]> wrote: > [ ... ] > It actually turns out that it is best to leave the objectClass values there > (I've discovered I have customers who are using the presence of the > objectClass value as an indicator of eligibility for some service). >
I thought you said that this caused breakage. If I understood correctly, keeping the objectclass without the deleted non-optional matching attribute(s) caused an erroneous situation. How did you address that or am I remembering incorrectly? Lucio.
