based on result of TS020771250 Hostname verification for WebSphere Application Server traditional Logs And stack trace

Hello

we ask an improvement about log and exception management , to reduce unusefulness logs or raise an alarm , without any kind of real issue.

//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

https://www.ibm.com/support/pages/node/7163109
Possible Side Effects

The changes introduced by PH58798 affect all outbound connections. This means that any outbound connection could potentially fail after PH58798 is applied if the host targeted by the outbound connection does not present a certificate with a SAN value that matches its hostname or IP address. Potential areas of impact include intra-cell communication, outbound calls from a WebSphere server to another middleware server such as a Database, or outbound calls from a web application running on a WebSphere server to any other host.

Here is an example of the type of error printed to the logs when a hostname verification failure occurs:

CWPKI0062E: SSL HANDSHAKE FAILURE: Host name verification error while connecting to host [example.ibm.com]. The host name used to access the server does not match the server certificate's [Subject Alternative Name [dnsName:notexample.ibm.com,dnsName:otherserver.ibm.com]]. The extended error message from the SSL handshake exception is: [No subject alternative names matching example.ibm.com found].

⚠️ The CWPKI0062E error alone may not always indicate a hostname verification error.  You need to check the extended error section of the output to confirm this wasn't thrown due to another exception.

//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

inner our case TS020771250 we discover no issues was present inner Environments and all certificate used to call two Security sources was OK ; but the product based on PH58798 write an exception that force to us to open the case and deep dive about the stack trace , that create effort to manage it. so the focus on CWPKI0062E , last sentence ; we need to ask an improvement and write it only when really the SSL Handshake go in error and the connection can't be established .

thank you