We are doing a rest call to a server with SSL in a job we originally built in 5.4 but it's now in 6.4. The SSL certificate only has one name in it (an FQDN accessible externally), and we need to access the server via another name. We can't change the certificate and need to accept this certificate.
We use tSetKeyStore to load the keys that we are using - and then a tRest component to make the request.
Note: "Check server identity" is not checked.
Exception in component tREST_1 (test)
com.sun.jersey.api.client.ClientHandlerException: java.io.IOException: HTTPS hostname wrong: should be <servername>
If I check the "Check server identity" it seems to work successfully. Any clue here why "check server identity" = true would fail when the servername is different?
It looks like an issue with the DefaultHostnameVerifier.
In tSetKeystore component, the "Check server identity" option is used to make the Job verify the match between the hostname of the URL and the hostname of the server. If they mismatch, the verification mechanism asks whether this connection should be allowed.