Interacting with External Event Systems › Deploy and Configure CA Automation Point Web Services › Configure a remote web service client for TLS

Configure a remote web service client for TLS

Once your server requires a TLS connection, configure your remote clients to use TLS connections. If you are not using the CA RequestService client, follow the TLS techniques for your chosen programming language. This document describes how to configure TLS for the RequestService client.

Since you specify the URI to RequestService, you control the use of TLS, because you specify https and the 8443 port number on your URI. To control the use of a keystore and/or truststore you must modify a Java properties file that is named RequestService.properties.

To modify that file in a client distribution, first copy the file from the directory:

YourClientUnzipDirectory\RequestService\distrib

To the directory:

YourClientUnzipDirectory\RequestService\Site\Config

If you are using the RequestService client on the AP server, copy the file from this directory:

%AP_HOME%\distrib

To the directory:

%AP_DATA%\Site\Config

Within the RequestService.properties file, you control the use of keystores and truststores by using the following property names:

com.ca.distauto.ap.websvc.client.keyStoreFile
com.ca.distauto.ap.websvc.client.keyStorePass
com.ca.distauto.ap.websvc.client.trustStoreFile
com.ca.distauto.ap.websvc.client.trustStorePass

With these properties, you can:

1. Validate server certificates against a client truststore that you have created.
2. Respond to a server request for a client certificate. A certificate is retrieved from a client keystore that you created, and the certificate is returned to the server.

You can specify that one of these two capabilities, both of them, or neither of them are enabled. A property is enabled if it is uncommented within the file and the property is assigned a value (Property=SomeValue). None of these properties are set by default. These default settings lead to the following behavior.

1. Server certificates are accepted but are not validated. No client truststore is needed.
2. The client does not return a client certificate to a server. No client keystore is needed.

Comments within the RequestService.properties file describe the detailed behavior of each property and the meaning of the value to which the property can be set.