VSE Recorder - Target failed to respond

Document ID : KB000094931
Last Modified Date : 16/10/2018
Show Technical Document Details
I am using the VSE Recoder to capture the transactions sent to the HTTPS endpoint, but I am not able to get a successful response from the Target System.
While recording the services with HTTP/S Transport Protocol we are getting "Target Failed to respond".
All Supported DevTest Releases.
When facing issues with the VSE Recorder, it is good to create a test case and verify if the Workstation is able to successfully communicate with the target endpoint.
If yes, we will probably be able to configure the VSE Recorder to capture the transactions between the client application and the endpoint.
If the test case is not able to get to the target endpoint, we need to verify what is preventing it. The VSE Recorder will also have problems to get to the target endpoint.

Some items that need to be verified:
1. Is it necessary to configure a proxy server in the Workstation for it to access the target endpoint?
If yes, please update the local.properties file with the following properties:
lisa.http.webProxy.host=<machine name or ip>

lisa.http.webProxy.ssl.host=<machine name or ip>

2. If the target endpoint is HTTPS, is the SSL handshake happening without issues?
We can use the HTTP/SSL Debug viewer to observe the details of HTTP and SSL activity in DevTest Workstation. This feature can be helpful in performing diagnostics.
To access HTTPS and SSL Debug Viewer documentation, please take a look at the following link: https://docops.ca.com/devtest-solutions/10-4/en/using/using-ca-application-test/using-devtest-workstation-with-ca-application-test/running-test-cases-and-suites/http-and-ssl-debug-viewer/
There is also more information regarding this feature in the link below:
javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure - https://comm.support.ca.com/kb/javaxnetsslsslhandshakeexception-received-fatal-alert-handshakefailure/KB000014151

In some cases, the TLS version being used by the Workstation is not what the server is expecting. In this case, we need to add the following property in the Workstation local.properties to use the correct TLS version:
for TLS version 1.2:
for TLS version 1.1:

It can also be that the server is requesting a client authentication - 2-way SSL authentication.
If that is the case, you will see a certificate request message under the ServerHello. Below an example:
*** CertificateRequest
Cert Types: RSA, DSS
Cert Authorities:
 ... ... <list of Cert Authorities the server trusts>
*** ServerHelloDone

In this case, we need to provide the client key for authentication under the Use SSL to Server field in the VSE Recorder.
User-added image