[ldap-sdk-announce] UnboundID LDAP SDK for Java 6.0.4

[Neil W. <nei...@pi...>]

We have just released version 6.0.4 of the UnboundID LDAP SDK for Java
<https://github.com/pingidentity/ldapsdk>. It is available for download
from GitHub <https://github.com/pingidentity/ldapsdk/releases> and
SourceForge <https://sourceforge.net/projects/ldap-sdk/files/>, and it is
available in the Maven Central Repository
<https://search.maven.org/search?q=g:com.unboundid%20AND%20a:unboundid-ldapsdk&core=gav>.
You can find the release notes at
https://docs.ldap.com/ldap-sdk/docs/release-notes.html, but here’s a
summary of the changes included in this version:

General Updates:


   -

   We fixed an issue with the Filter.matchesEntry method that could cause
   it to throw an exception rather than returning an appropriate Boolean
   result when evaluating an AND or an OR filter in which one of the nested
   elements used inappropriate matching (for example, if the assertion value
   did not conform to the syntax for the associated attribute type).



   -

   We fixed an issue with the way that decodeable controls are registered
   with the LDAP SDK. Under some circumstances, a thread could become blocked
   while attempting to create a new control.



   -

   We updated the JVM-default trust manager to properly check for the
   existence of a “jssecacerts” trust store file in accordance with the
   JSSE specification. It had previously only looked for a file named “
   cacerts”.



   -

   We updated the logic used to select the default set of supported cipher
   suites so that it will no longer exclude suites with names starting with
   “SSL_” by default on JVMs with a vendor string that includes “IBM”. IBM
   JVMs appear to use the “SSL_” prefix for some or all cipher suites,
   including those that are not associated with TLS protocols rather than a
   legacy SSL protocol. We also added a
   TLSCipherSuiteSelector.setAllowSSLPrefixedSuites method that can be used
   to override the default behavior.



   -

   We updated the LDIF reader to support reading modifications with
   attribute values read from a file referenced by URL. This was previously
   supported when reading LDIF entries or add change records, but it had been
   overlooked for LDIF modify change records.



   -

   We updated the LDIF reader so that it no longer generates comments
   attempting to clarify the contents of base64-encoded values if the value is
   longer than 1,000 bytes.



   -

   We updated the documentation to include the latest versions of the
   draft-behera-ldap-password-policy, draft-coretta-x660-ldap, and
   draft-ietf-kitten-scram-2fa specifications.



Updates Specific to Use With the Ping Identity Directory Server:


   -

   We added a new API for parsing access log messages generated by the
   server. The new API supports both text-formatted and JSON-formatted log
   messages, whereas the previous version only supported messages in the
   default text (“name=value”) format.



   -

   We updated the summarize-access-log tool (which can be used to perform
   basic analysis of server access log files) to add support for
   JSON-formatted log files.



   -

   We added support for retrieving and parsing X.509 certificate monitor
   entries.



   -

   We added client-side support for an administrative task that can cause
   the server to immediately refresh any cached certificate monitor data. The
   server will automatically refresh the cache every minute, but the task can
   be used to cause an immediate refresh.

-- 
_CONFIDENTIALITY NOTICE: This email may contain confidential and privileged 
material for the sole use of the intended recipient(s). Any review, use, 
distribution or disclosure by others is strictly prohibited.  If you have 
received this communication in error, please notify the sender immediately 
by e-mail and delete the message and any file attachments from your 
computer. Thank you._