By default, CA Advanced Authentication uses Transmission Control Protocol (TCP) to communicate with CA Risk Authentication Server. However, TCP is vulnerable to spoofing and man-in-the-middle attacks. By using CA Advanced Authentication, you can configure SSL to ensure secure communication between different components of CA Risk Authentication.
Note: See "Configuring SSL" for step-by-step configuration of SSL-based communication between different CA Risk Authentication components.
If you have configured SSL for secure communication, you can see the corresponding entries in the startup log files. The following table lists the log file entries when SSL is configured for CA Risk Authentication Server and Case Management Queuing Server protocols.
|
Protocol |
Entry in Log File |
|---|---|
|
CA Risk Authentication |
|
|
Server Management |
Started listener for [Server Management] [7980] [SSL] [srvmgrwsprotocol] |
|
Transaction Web Service |
Started listener for [RiskFort Trans WS] [7778] [SSL] [transwsprotocol] |
|
Administration Web Service |
Started listener for [RiskFort Admin WS] [7777] [SSL] [aradminwsprotocol] |
|
Native (SSL) |
Started listener for [RiskFort Native (SSL)] [7681] [SSL] [RiskFort] |
|
Case Management Queuing Server |
|
|
Case Management Queuing Administration |
Started listener for [Case Management Admin] [7780] [SSL] [srvmgrwsprotocol] |
|
Case Management Queuing Server |
Started listener for [Case Management Server] [7779] [SSL] [RiskFortCaseManagement] |
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|