Service Virtualization

Hello, I need to implement TLSv1.2 (It must be TLS. SSL is disabled company wide) anywhere in devtest where the username/password is entered:

• Portal
• Console
• Workstation

I have contacted CA support, but have yet to receive a response other than "we got your request" so i thought I would reach out to the community to see if anyone has faced a similar issue.

I Created my keystore, created my csr, got a signed ceritificate, imported the cert to the keystore, copied the cert to LISA_HOME renamed it to webserver.ks and updated my local.properties as follows:

https.protocols=TLSv1.2,TLSv1.1,TLSv1

 

lisa.net.bindToAddress=devtest5.XYZ.com
lisa.net.default.protocol=ssl
lisa.net.keyStore={{LISA_HOME}}webserver.ks
lisa.net.keyStore.password_enc=

 

# enable https and setup the webserver ssl keystore
 lisa.webserver.https.enabled=true
 lisa.webserver.ssl.keystore.location={{LISA_HOME}}webserver.ks
lisa.webserver.ssl.keystore.password_enc=
lisa.webserver.ssl.keymanager.password_enc=
 lisa.webserver.port=443

 

# should lisa workstation use https when launching the portals?
 lisa.portal.use_https=true
 lisa.portal.url.prefix=https://

I have also tried multiple variations and subsets of those properties

In IE i get the following error:

This page can’t be displayed

Add below property in ServiceImageManager.vmoptions/Workstation.voptions. This will work.

-Dhttps.protocols=TLSv1.1,TLSv1.2

Please refer to this link for the Firefox error:

https://www.namecheap.com/support/knowledgebase/article.aspx/807/69/firefox-error-code-sslerrorrxrecordtoolong 

You will also need to update the phoenix.properties for the Portal.

A support engineer will be contacting you today.

Hi SamManiscalco4211171,

Did either of these replies answer your question? If so, please be sure to mark the one that helped most as correct. If not, please give us a bit more info about the info you're looking for.

Thanks,

Melanie

Neither of the 2 proposed answers solved the question... I will add a comment with the solution

The main issues was that the keystore we were creating was not correct. Tips to make sure the key store is correct:

• Download and use the Portecle tool. it is basically a GUI for dealing with Java keystore. It is a lot easier to use
  • if using signed certs (not self signed) you need to 'import the CA reply'. NOT import the certs
• Use the workstation and create a web service execution step. Click the pro icon and select you java keystore - you can then verify that devtest is reading everything as you expected.

For selfsigned service recording by adding the following line in local.properties helped me https.protocols=TLSv1.2,TLSv1.1,TLSv1 

We use ServiceImageManager Service for recording thus added below properties in ServiceImageManager.vmoptions helped me resolve the issue. No need to update else where. If you record through workstation/ use live invocation in vsm you would need to add add the below property in their respective vmoptions file.

-Dhttps.protocols=TLSv1.0,TLSv1.1,TLSv1.2