Previous Topic: Enable SSL Between Java SDK and RiskMinder ServerNext Topic: Two-Way SSL


One-Way SSL

To set up one-way SSL between the Risk Evaluation SDK and RiskMinder Server, you must first configure the RiskMinder Native (SSL) protocol by using Administration Console and then configure the riskfort.risk-evaluation.properties file.

To configure one-way SSL between Java SDK and RiskMinder Server:

  1. Ensure that you are logged in as the MA.
  2. Activate the Services and Server Configurations tab in the main menu.
  3. Ensure that the RiskFort tab is active.
  4. Under the Instance Configuration section, click the Protocol Configuration link to display the Protocol Configuration page.
  5. Select the Server Instance for which you want to configure the SSL.
  6. In the List of Protocols section, click the Native (SSL) protocol link to display the page for configuring the protocol.
  7. Configure the following fields:
  8. Click the Save button.
  9. Restart RiskMinder Server:
  10. Navigate to the following location:
  11. Open the riskfort.risk-evaluation.properties file in an editor window of your choice.

    Note: Refer to appendix, "Configuration Files and Options" in the CA RiskMinder Installation and Deployment Guide for more information on the riskfort.risk-evaluation.properties file.

    1. Set the following parameters:
      • TRANSPORT_TYPE= SSL (By default, this parameter is set to TCP.)
      • CA_CERT_FILE= <absolute_path_to_Server_root_certificate_in_PEM_format>

      For example, you can specify one of the following:

      • CA_CERT_FILE=<install_location>/certs/<ca_cert>.pem
      • CA_CERT_FILE=<install_location>\\certs\\<ca_cert>.pem

      For example, you can specify CA_CERT_FILE= <install_location>/certs/<ca_cert>.pem.

      Important! In the absolute path that you specify, ensure that you use \\ or / instead of \. This is because the change might not work, if you use the conventional \ that is used in Windows for specifying paths.

    2. Save the changes and close the file.
  12. Restart the application server where your Java SDK is deployed.