Neil Wilson

We have just released version 7.0.4 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 added a “discard results” search result listener that can be used in cases where a search should be performed, but the actual matching entries...

We have just released version 7.0.3 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 fixed an issue in which the LDAP SDK did not properly handle certificates with a notBefore or notAfter timestamp that fell in the year 2049 if...

I assume that you’re asking about SSL-encrypted client connections using the LDAP SDK. In that case, there are two ways to do it: If you’re creating individual connections, then you’ll want to use a constructor that allows you to provide a SocketFactory, and then use SSLUtil to create an instance of an SSLSocketFactory. If you’re creating a connection pool, then you’ll probably want to use a ServerSet to create the connections, and you would configure your ServerSet with the appropriate SSLSocketFactory....

To do this, you’ll create your own custom LDAPListenerRequestHandler, not unlike the ProxyRequestHandler. You can absolutely use that as your model for creating your new version. The LDAPListener framework would handle all of the work of accepting connections, creating an LDAPListenerClientConnection for each of them, and in the process would invoke your request handler’s newInstance method so that you can create an instance of your request handler that is specifically intended for dealing with communication...

You shouldn’t be creating LDAPListenerClientConnection objects in your code. LDAPListenerClientConnection instances should only be created by LDAPListener, and they’re used to maintain all the state around a client connection that is established to the LDAPListener. And in the course of creating an LDAPListenerClientConnection, it calls LDAPListenerRequestHandler.newInstance to create a new instance of the request handler that is specifically to be used in interacting with that connection.

We have just released version 7.0.2 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 added support for using the 2.x version of the Bouncy Castle FIPS-compliant security provider, which provides support for FIPS 140-3 compliance....

We have just released version 7.0.1 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 added a new MaximumIdleDurationLDAPConnectionPoolHealthCheck class that can be used to replace connections that have remained idle for longer than...

The LDAP SDK itself never throws this exception. The JVM will throw it if you've set the SO_TIMEOUT socket option (which says that a read operation should not be allowed to block for more than the specified length of time), and if an attempt to read data from the associated socket doesn't yield any results within the allotted time period. This is a completely normal condition that the JVM happens to use an exception to convey. The LDAP SDK does look for this exception being thrown, and if it encounters...