UnboundID LDAP SDK for Java 7.0.6

We have just released version 7.0.6 of the UnboundID LDAP SDK for Java. It is available for download from GitHub and SourceForge, and it is available in the Maven Central Repository. You can find the release notes for this release (and all previous versions) at https://docs.ldap.com/ldap-sdk/docs/release-notes.html, but here’s a summary of the changes:

• We improved the logic used by the Attribute.nameIsValid methods. These methods are used to determine whether a given string represents a valid attribute description, which include an attribute type name or OID and an optional set of attribute options. Previously, this method could incorrectly reject names with valid attribute options (those starting with digits or a hyphen), and it also didn’t support attributes identified by a numeric OID.

• We added an Attribute.baseNameIsValid method, which can be used to determine whether a given string represents a valid attribute type name or numeric OID.

• We added an Attribute.optionNameIsValid method, which can be used to determine whether a given string represents a valid attribute option name.

• We added a VerifyChainSignaturesTrustManager class, which can be used to verify the signatures in a presented certificate chain. This trust manager expects the end-entity certificate to be the first certificate in the chain, and it ensures that it’s possible to build a trust path using the other provided certificates. For the sake of leniency and compatibility with other implementations, if a certificate is present multiple times in the chain, then the duplicates are ignored, and we also don’t require subsequent certificates in the chain to be presented in the correct order.

• We permanently disabled auto-reconnect functionality for LDAP connections. This ability had been officially deprecated for over ten years, as it was very fragile and could only work in a limited set of circumstances. The associated methods are still in place to preserve API compatibility, but attempting to enable auto-reconnect no longer has any effect. In cases where you want to use automatic retry functionality, use an LDAP connection pool instead of an individual connection, and use the setRetryFailedOperationsDueToInvalidConnections method to indicate that operations should be retried on a newly established connection if it fails in a way that may indicate that the existing connection is no longer valid.

• We updated the collect-support-data command-line tool, extended request, and administrative task to add an option to exclude Java Flight Recorder (JFR) ata from the resulting archive. This may be useful in cases where collect-support-data should run as quickly as possible, or should generate a smaller archive file.

• We updated the BouncyCastleFIPSHelper class to add a couple of constants to make it easier to use the LDAP SDK in conjunction with bc-fips version 2.1.3. This library introduced attempts to use certain native CPU instructions, but that seems to adversely affect reliability on certain platforms.

• We updated the documentation to include the latest versions of the draft-codere-ldapsyntax, draft-housley-asn1-layman-guide, draft-ietf-kitten-password-storage, draft-ietf-kitten-sasl-ht, and draft-melnikov-sasl2 drafts.