This is a typical answer to OSS ticket concerning this issue:
"A strict server name check is first performed in the SSL handshake,
before any certificate chain is verfied against the certificates in the
Trusted CA keytore view.
The strict server name check means that the CN in the server certificate
must exactly match the host name in the request URL.
In this step, the certificates in the client (J2EE engine) Trusted CA
keystore view are not yet involved.
You'll either need to configure the host name, as the CN of the
server certificate or create the server certificate with the CN (and
import/use it in the server), as you plan to use it in the FTP Adapter
receiver channel configuration.
Please ensure your channel configuration uses the hostname expected
by the server. i.e. that you are also using: *.sap.com
and that this FQHN is used consistently.
If you still have problems, please note that the FTP protocol itself
has no concept of hostnames, so an FTP client is reliant on the IP
address of the server to obtain the hostname. If any reverse DNS
lookup is taking place during the processing on your network, you need
to ensure the DNS lookup returns the FQHN of your FTP server, which
is: *.sap.com
Try run the scenario using a public certificate and adding the IP
address and host name to the host file."
Hope that helps
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.