RiskMinder Java Developer's Guide › Additional SDK Configurations › RM_3.1--SSL Communication Between RiskMinder Components

RM_3.1--SSL Communication Between RiskMinder Components

In addition to supporting TCP-based communication between RiskMinder Server and the SDKs, RiskMinder also supports Secure Socket Layer (SSL) for secure communication between these components. RiskMinder can be configured for one-way Secure Socket Layer (SSL) with server-side certificates or two-way SSL with server-side and client-side certificates between the Server and SDKs, as shown in the following figure.

Although the default mode of communication is TCP, RiskMinder Server supports SSL communication (two-way as well as one-way) with the following components to ensure integrity and confidentiality of the data being exchanged during a transaction:

• Case Management Queuing Server
• RiskMinder Database
• User Data Service
• RiskMinder Risk Evaluation SDK
• Sample Application
• Evaluation Callout
• Scoring Callout

Note: RiskMinder enables you to write your own custom Evaluation rule, based on your business requirements. This custom rule is called Evaluation Callout. Similarly, RiskMinder also enables you to write your own custom Scoring logic called Scoring Callout.
Refer to CA RiskMinder Administration Guide for more information on these Callouts.