Neil Wilson

Thanks for reporting this. We don't currently take third-party contributions to the LDAP SDK, but we'll look into providing our own solution to this. We'll be releasing the 3.1.1 version...

A fix for this should now be committed in the public repositories.

The problem is that you're trying to create an extensible matching filter, but you're using a method to create an equality filter. Those are two completely different types of filters,...

In general, the in-memory directory server was designed to be mostly standards-compliant and didn’t have any support for UnboundID/Ping-proprietary controls, extensions, or SASL mechanisms. However, the ignore NO-USER-MODIFICATION control is...

I’ve looked into this, but haven’t been able to reproduce the problem that you’re describing. I can write a simple Java program that uses TLSv1 or TLSv1.1 to interact with...

Thank you, but at the current time, we do not accept third-party contributions to the LDAP SDK.

I've just committed an update to the GSSAPIBindRequest class that refreshes the configuration before creating the LoginContext. Could you please test it and verify that it works as expected in...

The 5.0.0 release of the LDAP SDK is now available and includes the fix for this issue.

In general, you should not create search filters by constructing their string representations. Instead, you should programmatically construct them from their individual components. In the case of the filter you...

And for the record, the correct way to escape a comma in a search filter is with "\5c,". That is, you escape the backslash as "\5c" and leave the comma...