openldap-bugs December 2025

openldap-bugs@openldap.org

1 participants
204 discussions

[Issue 7047] slapd crash on bad indexed translucent
by openldap-its＠openldap.org 02 Dec '25

02 Dec '25

https://bugs.openldap.org/show_bug.cgi?id=7047 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |SUSPENDED --- Comment #7 from Quanah Gibson-Mount <quanah(a)openldap.org> --- suspending as no reports since move to lmdb -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 6942] updateref config is inadequate
by openldap-its＠openldap.org 02 Dec '25

02 Dec '25

https://bugs.openldap.org/show_bug.cgi?id=6942 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|2.7.0 |2.8.0 -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 6531] Modify updateref to generate referrals on the backend
by openldap-its＠openldap.org 02 Dec '25

02 Dec '25

https://bugs.openldap.org/show_bug.cgi?id=6531 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|2.7.0 |2.8.0 -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 10409] New: Implement password policies for the rootdn
by openldap-its＠openldap.org 02 Dec '25

02 Dec '25

https://bugs.openldap.org/show_bug.cgi?id=10409 Issue ID: 10409 Summary: Implement password policies for the rootdn Product: OpenLDAP Version: 2.6.10 Hardware: All OS: All Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: slapd Assignee: bugs(a)openldap.org Reporter: 31621968(a)qq.com Target Milestone: --- We have successfully configured the Password Policy overlay (ppolicy) on our OpenLDAP server. This configuration ensures that accounts are locked after exceeding the maximum number of failed bind attempts, as defined by the policy. For example, if the ppolicy is set to lock an account after 5 failed bind attempts, the server enforces this behavior effectively for all users under the ppolicy scope. However, we have observed that the rootdn user does not seem to be subject to these same password policies. Specifically, even when the rootdn exceeds the maximum number of failed bind attempts, it does not get locked or restricted in any way. We would like to know if there is a way to apply the same password policies (e.g., account locking after failed bind attempts) to the rootdn. -- You are receiving this mail because: You are on the CC list for the issue.

1 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs December 2025