Page History

...

<Connector port="9443" maxHttpHeaderSizeprotocol="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"org.apache.coyote.http11.Http11NioProtocol"
               connectionTimeout="20000"
               enableLookups="false" disableUploadTimeout="true"
acceptCount="100" scheme="https" secure
               maxThreads="150"
               SSLEnabled="true"
clientAuth               scheme="falsehttps" sslProtocol
               secure="TLStrue"
keystoreFile="C:/Path To Keystore/virtualize.pfx"
keystorePass="security" keyAlias="virtualize" keystoreType="PKCS12" truststoreFile="../lib/cacerts"
truststorePass="changeit" truststoreType="JKS" />

keystoreFile

>
        <SSLHostConfig>
            <Certificate certificateKeystoreFile="conf/server-keystore.jks"
                         certificateKeystorePassword="changeit"
                         certificateKeyAlias="virtualize"
                         type="RSA"/>
        </SSLHostConfig>
</Connector>

certificateKeystoreFile

The certificateKeystoreFile 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 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.

keystorePasscertificateKeystorePassword

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

keyAliascertificateKeyAlias

Set the keyAlias attribute certificateKeyAlias attribute to point to the alias of the certificate/private key pair.

keystoreTypetype

Set the keystoreType to the type 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 trust store used for validating client certificates should be specified using the truststoreFile, truststorePass, and truststoreType attributes:

...

 in the SSL HTTP/1.1 Connector entry in server.xml. For example:

<Connector port="9443" protocol="org.apache.coyote.http11.Http11NioProtocol"
               connectionTimeout="20000"
               enableLookups="false"
               maxThreads="150"
               SSLEnabled="true"
               scheme="https"
               secure="true">
        <SSLHostConfig sslProtocol="TLS"
                       truststoreFile="conf/server-truststore.jks"
                       truststorePassword="changeit"
                       truststoreType="JKS"
                       certificateVerification="required"
                       protocols="all">
            <Certificate certificateKeystoreFile="conf/server-keystore.jks"
                         certificateKeystorePassword="changeit"
                         certificateKeyAlias="virtualize"
                         type="RSA"/>
        </SSLHostConfig>
</Connector>

...

Additional Configuration Details

...