As part of our environment hardening Windows AD LDAPS TLS1.0 has been disabled and TLS1.1 has been enabled.
This caused OO to stop authenticating properly using AD LDAPS TSL1.1 PORT 636
In case LDAPS port 636 TLS1.0 is enabled, TLS1.1 is disabled everything works properly
In case LDAPS port 636 TLS1.1 is disabled, TLS1.1 is enabled - stops working
All certificate chains are imported into client.trustore file
The error thrown in the log is misleading.
2017-05-29 07:15:31,285 [http-nio-8443-exec-8] (LdapUtils.java:104) ERROR - Failed to initialize an SSL connection.The server certificate may not be imported into the Central truststore: An error occurred while attempting to connect to server server.xx.com:636: java.net.SocketException: Connection reset
2017-05-29 07:15:31,285 [http-nio-8443-exec-8] (LdapV2Controller.java:128) ERROR - Failed to initialize the SSL connection
com.hp.oo.security.authn.exceptions.SslException: Failed to initialize the SSL connection
An hotfix is available with Support -> HF_QCCRID33279