Virtual Service not Picking up Custom Keystore

Products

• Service Virtualization

Issue/Introduction

Displaying virtual service URL from browser shows this error:

Environment

All supported DevTest releases.

Cause

When a virtual service is not picking up a custom keystore, it is typically because the service model is still configured to use the default vse.ks keystore.

Resolution

To resolve this, you must update the virtual service model (VSM) to explicitly point to your custom keystore on the VSE server and redeploy it.

1. Download the virtual service from the Portal.

2. Open up the mar in your Workstation.

3. Open the Listen step.

4. Click the Use SSL to Client checkbox to true.

5. In the SSL keystore file field put the full path to the keystore file on the VSE server.

NOTE:  Ensure the keystore file is placed in a directory accessible by the VSE server. If you encounter a "Cannot load keystore" error, verify that the file path is correct on the server itself, as relative paths from your local machine will not work during deployment 

6. Enter Click the Password Editor gear icon and enter the password of the keystore.

7. Save the VSM.

8. Delete the mari file for that VSM.

9. Create MAR Info File

10. Deploy the VSM.

You will have to do this for every virtual service wanting to now use the custom keystore.

In the future if you need to make a change to the keystore, the virtual service needs to be redeployed or VSE needs to be restarted.