Page History

...

In any case, Virtualize can be configured to accept incoming HTTPS connections on port 9443 (default SSL connector) or another port. 

Configuring server.xml

After obtaining your certificate and private key, you need to configure the Virtualize server's underlying Tomcat instance to use them. This requires editing the server.xml configuration file.

• For desktop client users, refer to the product’s provided server.xml located at: <INSTALL-DIR>/plugins/com.parasoft.ptest.libs.web_<VERSION>/root/tomcat/conf 
• For WAR file deployments, update the server.xml located in: <TOMCAT_HOME>/conf

SSL details can be configured by modifying the SSL HTTP/1.1 Connector entry in server.xml. For example:

<Connector port="9443" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" disableUploadTimeout="true"
acceptCount="100" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLS"
keystoreFile="C:/Path To Keystore/virtualize.pfx"
keystorePass="security" keyAlias="virtualize" keystoreType="PKCS12" truststoreFile="../lib/cacerts"
truststorePass="changeit" truststoreType="JKS" />

keystoreFile

The keystoreFile attribute specifies the location of the keystore file that contains the Virtualize server’s private key and SSL certificate. This file is essential for enabling HTTPS, as it allows the server to identify itself securely to clients. The value depends on your configuration option. 

• If using Option 1 (preferred) or Option 2: Specify the path to the keystore file you generated for the Virtualize server. Although the keystore paths can be relative to the location of the server.xml file, it is best to provide absolute paths in order to ensure correct configuration.
• If using option 3: Specify the path to the keystore file used by the real SSL-based service that you want to emulate. Use forward slashes (/) instead of backward slashes (\). For example, C:/Users/myUser/keystore.jks.
• If using option 4: No change is needed for the keystoreFile attribute, since the AUT will accept any server certificate.

keystorePass

Set the keystorePass attribute to be the password to your keystore.

...

Set the keystoreType to the type of keystore you are using, such as PKCS12, JKS, BKS, UBER, or PEM.

clientAuth

Two-Way SSL (Mutual Authentication)

For two-way SSL (mutual authentication), the clientAuth attribute must be set to true and the truststore used for validating client certificates should be specified using the truststoreFile, truststorePass, and truststoreType attributes:

• Set clientAuth to true to require clients (AUT) to present a certificate.
• Modify truststoreFile to point to your keystore file. Use forward slashes (/) instead of backward slashes (\). For example, C:/Users/myUser/keystore.jks.
• Modify truststorePass to be the password to your keystore.
• Modify truststoreType to PKCS12, JKS, BKS, UBER, or PEM, depending on the type of keystore you're using.

Additional Configuration Details

...