Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect Rational Directory Server (Tivoli) & Rational Directory Administrator.

To improve the robustness of LDAPS (secure LDAP over TLS) connections, endpoint identification algorithms have been enabled by default. There may be situations where some applications that were previously able to successfully connect to an LDAPS server may no longer be able to do so.
With this LDAP update, LDAP is asking JSSE to validate the LDAP server's certificate to ensure it is compliant with hostname verification.  With this change, if the server's certificate is not compliant, then exception will be thrown.  In the past, LDAP did not request JSSE to perform hostname verification and a non-compliant server certificate would not have had caused an issue.
In order to resolve the issue, Regenerate the RDS server certificate(tdsserverkey.kdb) so that the certificate's subject name or certificate's subject alternate name matches the RDS server hostname, by following instructions from technote:
 
How can I generate my own 'tdsserverkey.kdb' keystore for TLSv12 communication and use it in a IBM Rational Directory Server (Tivoli) deployment?
 
After regenerating the RDS Server certificate matching with the RDS Server Hostname, use FQDN's wherever applicable.
E.g. : RDA Login Screen, Creating RDS Partition and DOORS to RDS Connection.
 
(If you have already regenerated the RDS Server certificate by following above technote, while upgrading to IBM JRE versions 7.1.4.30 or later or 8.0.5.20 or later, then no need to follow the technote again)