Has the memberof overlay been replaced with something else? I couldn't
find anything in overlays/README and the roadmap.
-------- Forwarded Message --------
Subject: [Issue 9795] New: Remove memberof overlay
Date: Wed, 02 Feb 2022 20:02:51 +0000
Issue ID: 9795
Summary: Remove memberof overlay
Target Milestone: ---
The memberof overlay was deprecated with the release of OpenLDAP 2.5. It
should be removed prior for the next minor release (i.e., 2.7)
You are receiving this mail because:
You are on the CC list for the issue.
Hope everyone is doing well.
Our current environment:
3-way MMR (syncrepl) with centos 7 using v2.6
We want to add a 4th master but with Rocky Linux 8.
Why rocky? because eventually we will migrate the 3 masters to rocky linux too. But that will take some time…
Any concerns with mixing linux flavor but using same openldap version?
Dont do it?
Any input is appreciated.
I like to implement an autogrow functionality for LMDB.
The documentation for mdb_env_set_mapsize says that no transactions should
be active when using this function.
When looking at the code I can see that the function only checks if there is
an active WRITE transaction and in this case it returns an error.
Is it possible to reuse existing READ transactions or even associated
cursors after mdb_env_set_mapsize has been called?
Thank you and best regards,
I just discovered a minor typo in my version of the slapo-ppolicy manual page (possibly it's fixed alrerady):
The manual page lists "pwdGraceAuthnLimit", but the attribute returned by slapcat is "pwdGraceAuthNLimit" (different case for 'N')
The name from the schema also is "pwdGraceAuthNLimit".
I have a question regarding password rules that are enforced when a user changes their password in OpenLDAP. We have a need to implement a dictionary rule whereby words and phrases in a dictionary are not allowed in a users password. I am not able to see currently where such functionality exists in OpenLDAP and am wondering if there are any extensions to OPenLDAP that were developed to support this or if it would be required to write code to support this feature?