In the latest release of the Vordel Gateway, v6.0.3, we added the option for the Gateway to check if a certificate's Common Name matches the hostname of the machine using it. What does this mean?
Sometimes internal machines are setup with SSL certificates which don't match their hostnames. Usually the reason is because the organization has bought a block of certs from Verisign, doesn't want to order more, and doesn't want to use self-signed certificates. So if you are putting the Vordel Gateway in front of a machine which (for one reason or another) is using an SSL certificate which doesn't match its hostname, then you can tell the Gateway to either (a) flag this as an issue with the service and block the request, or (b) ignore the problem.
The setting is under the "Remote Hosts" setting in Policy Studio, and the checkbox is "Verify server's certificate matches requested hostname".