Just a quick follow up to close the loop on this bug we encountered. Thanks to your
advice, we found that we could correct the behavior after upgrading our 389DS servers to
the latest version available in the epel-release repository: 389-Directory/1.4.3.231
B2021.322.1803 in combination with correcting our local and global policies such that they
were no longer conflicting. We basically removed the local policies, set the global
policy, and setup a single local policy exception for the global policy.
David MakĀ (Pronouns: He/Him/His)
Identity Services Specialist
Information Technology Services
Northeastern University