Start Up Log Entries used with SSL
By default, uses Transmission Control Protocol (TCP) to communicate with Risk Authentication Server. However, TCP is vulnerable to spoofing and man-in-the-middle attacks. By using , you can configure SSL to ensure secure communication.
aa91
By default,
Symantec Advanced Authentication
uses Transmission Control Protocol (TCP) to communicate with Risk Authentication Server. However, TCP is vulnerable to spoofing and man-in-the-middle attacks. By using Symantec Advanced Authentication
, you can configure SSL to ensure secure communication.If you have configured SSL, you see the corresponding entries in the startup log files. The following table lists those log file entries:
Protocol | Entry in Log File |
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] |