389 Directory Server 1.4.3.12

The 389 Directory Server project has released version 1.4.3.12. Changes in this release include:

  • Fixed an issue that could prevent the use of TLSv1.3.
  • Fixed an issue that could cause backup to fail if the database directory was set with the server online.
  • Fixed an issue that could cause multiple entries to have the same entryUSN value.
  • Prevent an issue that allowed deleting a managed entry.
  • Provided separate monitor entries for each Berkeley DB backend.

389 Directory Server 1.4.4.4, 1.4.3.11, and 1.4.2.16

The 389 Directory Server project has announced new releases of versions 1.4.4.4, 1.4.3.11, and 1.4.2.16. From the release announcements, it looks like some of the changes in these versions are:

  • Fixed an issue that could cause a certificate private key to be written in PEM form to an incorrect location (version 1.4.4.4)
  • Fixed memory leaks in disk monitoring (all three versions)
  • Added OpenLDAP syncrepl compatibility (version 1.4.4.4)
  • Added support for the entryUUID attribute (version 1.4.4.4)
  • Added new “wtime” and “optime” access log fields and updated the logconv analysis tool to support them (all three versions)
  • Added an option to reject internal unindexed searches (versions 1.4.3.11 and 1.4.4.4)
  • Improved autotune defaults (version 1.4.4.4)
  • Fixed an issue that could prevent dsidm from deleting an organizational unit (all three versions)
  • Fixed an issue that could cause a UI crash when attempting to manage attribute uniqueness for an empty subtree (all three versions)
  • Added an error log message when processing a fully unindexed search (all three versions)
  • Added a warning log message when the configured thread number is significantly different from the auto-tuned value (all three versions)
  • Fixed an issue in which the reindex task could create an abandoned index file (all three versions)
  • Fixed an issue with the dsctl tool when working with instance names containing “slapd-” (all three versions)
  • Fixed an issue that could cause db2ldif to crash if an LDIF file can’t be accessed (versions 1.4.3.11 and 1.4.4.4)
  • Fixed an issue that prevented creating a naming context with the countryName attribute type (version 1.4.4.4)
  • Fixed issues with the healthcheck tool (version 1.4.4.4)
  • Fixed an issue with the sambaConfig object class OID (version 1.4.4.4)
  • Reduced lock contention when creating a connection mutex (version 1.4.4.4)
  • Fixed an issue in which an entry could be missing a DN (version 1.4.4.4)
  • Updated healthcheck to look for additional “notes” values in the access log (version 1.4.4.4)
  • Set a default minimum number of worker threads (version 1.4.4.4)
  • Fixed an issue that could allow a user to alter the pwdReset attribute (version 1.4.4.4)
  • Fixed an issue that could cause the cn=monitor entry to report an incorrect numSubordinates value (version 1.4.4.4)
  • Fixed an issue that could prevent dsctl and dsidm from reporting errors correctly when using a JSON output format (version 1.4.4.4)
  • Added the labeledURIObject object class to the server schema (version 1.4.4.4)
  • Enable samba schema by default (version 1.4.4.4)

LdapRecord 1.9.0

LdapRecord aims to provide a simple way to interact with LDAP entries using PHP. The project has just released version 1.9.0, which appears to include the following changes over the previous 1.8.2 version:

  • Improved support for Active Directory accounts for users with an Exchange mailbox
  • Improved support for searches using DNs
  • Fixed issues with support for large groups
  • Added support for local model query scopes

LDAP Tool Box Service Desk 0.3

The LDAP Tool Box project provides a set of LDAP-related applications, administrative tools, and other utilities. They have just released the 0.3 release of their Service Desk tool, which is a web application for administrators that supports viewing and managing accounts in an LDAP directory server. This release includes the following changes:

  • Added support for locking accounts by setting a specific value in the pwdAccountLockedTime attribute
  • Fixed an issue in which it did not properly handle the case in which the pwdAccountLockedTime attribute was set but pwdLockoutDuration was missing or zero

Note that because these operations are not standardized, they will only be available for certain types of directory servers.

LdapRecord 1.8.2

LdapRecord aims to provide a simple way to interact with LDAP entries using PHP. The project has just released version 1.8.2, which appears to include the following changes since the 1.8.0 version that I previously reported on:

  • Fixes an issue with conflicting variable names in a relation method
  • Fixes an issue that could arise when searching for a user when the search included credentials