Steffen, Is it also possible to test your stuff with jdk1.8.0_51 so that we will know something must be wrong with security in jdk1.8.0_51? Appreciate your help Ambica.
-----Original Message----- From: Sanka, Ambica [mailto:asa...@atpco.net] Sent: Monday, July 18, 2016 11:00 AM To: Tomcat Users List <users@tomcat.apache.org> Subject: RE: java Thanks Steffen for letting me know. Did you also post your issue in java community? Did you get any response? Currently we are using 1.8.0_45. In the future we have requirement to upgrade and got stuck here. -----Original Message----- From: Steffen Heil (Mailinglisten) [mailto:li...@steffen-heil.de] Sent: Monday, July 18, 2016 10:55 AM To: Tomcat Users List <users@tomcat.apache.org> Subject: AW: java Hi > With jdk 1.8.0.45 our ldap communication is giving results. As soon as > we change tomcat to use jdk1.8.0_51, I am getting below exception. I > am not sure security changes in jdk 1.8.0_51 preventing the ldap certificate > loaded in cacerts in java not communicating properly to our ldap server. I am not sure that this related, be we were having issues after updating from 1.8.0_31 to 1.8.0_72 with certificates signed by root-cas that have a md5 signature. While the CA signature in the CA certificate does not provide any security, a bug in the jre rejected the certificate even though the certificate itself was signed with sha1. Maybe this is related. Regards, Steffen --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
