Adldap2 10.2.0

Adldap2 is a PHP package that provides LDAP authentication and directory management tools. The project has just released version 10.2.0, which fixes an issue that could yield different results across different types of directory servers, improved support for user account control on Active Directory, and made it easier to interact with the Active Directory userPrincipalName attribute.

389 Directory Server Versions 1.4.0.30, 1.4.1.9, and 1.4.2.3

The 389 Directory Server project has released announced three new releases, for versions 1.4.0.30, 1.4.1.9, and 1.4.2.3. According to the release notes for each version, some of the changes include:

  • Fix a potential crash when retrieving information about nonleaf entries (all three versions)
  • Fix a potential crash on SUSE Linux with SELinux (versions 1.4.0.30 and 1.4.1.9)
  • Fix a potential crash in SASL bind processing (version 1.4.2.3)
  • Fix an etime formatting issue in access log messages (all three versions)
  • Fix an issue in which the server may fail to log an error message when failing to parse an object class (all three versions)
  • Ensure that the requested base DN is logged when a search is rejected because of an invalid attribute (version 1.4.2.3)
  • Improve task handling during shutdown (all three versions)
  • Add support for subtree searches with a base DN of the null DN (version 1.4.2.3)
  • Improve performance when trying to retrieve information about nonleaf entries (all three versions)
  • Clean up CLI error output (all three versions)

Ping Identity Directory Server 7.3.0.3

The Ping Identity Directory Server version 7.3.0.3 has been released and is available for download. The release notes are available online, but this version addresses two issues:

  • If an attempt to establish an outbound LDAP connection failed, the server could leak a small amount of memory. Over time, these small allocations could accumulate and could cause the JVM to run out of memory.
  • In a Directory Proxy Server configured to use entry balancing, a search that spanned multiple backend sets could incorrectly return a result of success if all search attempts within one of the backend sets failed with a timeout. It now returns a result of unavailable.