Configure the VSE Recorder when target system is configured for 1-way SSL

Products

• CA Application Test
• CA Continuous Application Insight (PathFinder)
• Service Virtualization

Issue/Introduction

This document describes how the VSE Recorder in the Workstation needs to be configured to interact with a target endpoint that is configured for 1-way SSL authentication - server side authentication.

Environment

All Supported DevTest Releases.

Resolution

When using the VSE Recorder with the Workstation, it is a good idea to create a test case and verify if the Workstation is able to get a valid response from the target endpoint.

For a HTTPS request, we can use the Web Service Execution or the REST step.

Here is the documentation for these two steps:

Web Service Execution Step: Refer to section "Web Service Execution (XML) Step" in the documentation of the DevTest release you are running.
REST step: Refer to section "REST Step" in the documentation of the DevTest release you are running.

If the response is not valid, we need to verify what is happening. If the test step is not receiving a proper response it is most likely the VSE Recorder will face the same.

After we confirm the Workstation is able to connect and get a valid response from the target endpoint, start the VSE Recorder.

Provide the basic information for VSM and VSI names. The Transport Protocols will be HTTPS.

In the next screen, for the target host and port provide the target hostname and port. Do not provide the entire URL for the target hostname, just the endpoint domain name is enough.
Since the endpoint is expecting HTTPS requests, we will need to select "Use SSL to Server". "Use SSL to Client" is optional.

If only "Use SSL to server" is selected, the communication between the client application and the VSE Recorder will the plain HTTP, but the VSE Recorder will communicate with the target endpoint using HTTPS.
In this case, the client application needs to send HTTP requests to the VSE Recorder.

If "Use SSL to client" is selected as well, the communication between the client application and the VSE Recorder will be HTTPS as well as the communication from VSE Recorder to the target endpoint.
In this case, the client application needs to send HTTPS requests to the VSE Recorder.
 

If these SSL options are not selected at all, the communication with the VSE Recorder and target system will be plain HTTP. In case the target endpoint is expecting HTTPS requests, we won't be able to get valid responses if SSL is not used in the recorder.

The options to provide a keystore will enabled when the SSL options are selected. You can leave the default keystore already set or provide a different key.
More details about this process can be found here: Refer to section "HTTP/S Transport Protocol" in the documentation of the DevTest release you are running.

After the VSE Recorder is configured, select Next and the recorder will be in captured mode, listening for transactions in the specified listen port.

Go back to the client application and send the requests to the machine where the VSE Recorder is running in the port the VSE Recorder is listening.

Additional Information

More information regarding SSL and DevTest: https://community.broadcom.com/enterprisesoftware/viewdocument/of-ssl-sni-java-and-devtest?CommunityKey=94bda077-625b-4914-8ac3-c88a06c2cc23&tab=librarydocuments

DevTest documentation for SSL with VSE Recorder:  Refer to sections "SSL with VSE Recording" and "HTTP/S Transport Protocol" in the documentation of the DevTest release you are running.