I tried both solutions, with or without boundled libraries, but connection still fails when I try to use ldaps.
In ccnet.log, there is:
ldap_bind failed for user Manager: Can’t contact LDAP server.
A tshark examination of the traffic to and from the ldaps server shows that after SYN, SYN ACK, the client immediately send a FYN.
As described earlier, I also tried to remove the bundled libraries without success. We have bought a valid pro license and like to get ldaps work again. The fact that ldapsync works with ldaps makes me think that it should not be a big problem to make ldapbind also work again.
Now the package is built on CentOS 6. So there could be binary compatibility problem with CentOS 7’s ssl related libraries. We’ll build it for CentOS 7 soon. I think that would solve the problem.
Now, half a year after the problem first occured, it is still not resolved. I just installed the latest Seafile pro 6.1.9 and still can not connect via LDAPS to our ldap server on RedHat 7.3.
You should really take the time to create the CentOS 7 packages, because this is getting a security issue. Now the GLIBC packages are depending on the newer NSS and NSPR libraries. Until now one could hold back only the relevant libraries to keep Seafile working with LDAP authentication. Now it means you cannot update nearly a single package… Please raise the priority for this problem!
Could you please share the knowledge how to get LDAPS to work on CentOS 7 ? I’ve just updated Seafile to 6.2.5 and still no luck – “Can’t contact LDAP server”. With LDAP works OK.