Neil Wilson

@totaljfb Could you describe your test case? Is it something that could be converted into a standalone program for testing? To use the LDAP SDK in synchronous mode, you need...

@totaljfb are you intentionally closing and re-establishing the connection at any point in the process, or are you just trying to continue using a connection that had previously been used...

It seems unlikely that the StartTLS change you pointed out is responsible for the problem, as that only affects client connections that the LDAP SDK establishes and wouldn't apply to...

If that's the case, then it's almost certainly related to the JVM's implementation of TLSv1.3 rather than something in the LDAP SDK itself. The LDAP SDK doesn't implement TLS logic...

The javax.naming package is part of JNDI, but the UnboundID LDAP SDK for Java is a completely independent API for interacting with LDAP directory servers. It does not use JNDI...

I've just committed something that should fix this, as well as for the `addEntries(String...)` method. As a workaround, instead of using: ``` server.importFromLDIF(false, path)` ``` You could use: ``` LDIFReader...

I’m aware that that DIGEST-MD5 has been declared historic (and also CRAM-MD5 via [draft-ietf-sasl-crammd5-to-historic](https://docs.ldap.com/specs/draft-ietf-sasl-crammd5-to-historic-00.txt)). I certainly don’t recommend their use, but I’m not going to remove support for them in...

This was intentional. Even if a schema entry contained one or more unparsable elements, we still wanted to make it possible to retrieve whatever valid schema elements there were in...

Thanks for the offer of assistance, but it’s Ping Identity’s policy to not accept third-party code. However, bug reports and feature requests are definitely welcome.

This should be addressed by the changes committed in https://github.com/pingidentity/ldapsdk/commit/c0d016fde736cb155c2011c2a9fb45623151187d