Troubleshoot Two-Way SSL Connections

If the test connection fails because two-way SSL communication didn't happen correctly, note that different servers may respond differently. The following two different behaviors are identified, but there can be other variations. When you test the connection on the Connections page, both of these cases are reported as failures.

  • If a proper client certificate wasn't presented by the AS2 Adapter, the remote server can close the TCP connection unilaterally. On the client side, no response is received. The server instead closes the connection abruptly.
  • A remote server may send a response with an HTTP status code such as 400 (bad request) or 403 (forbidden). The server may or may not include the reason in the response.