FortiGate
FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
jfelix09
Staff
Staff
Article Id 335611
Description This article describes how to secure the connection between a TS-Agent and an FSSO-Collector Agent (Windows and FortiAuthenticator).
Scope TS-Agent and FSSO Collector Agent, FortiGate, FortiAnalyzer.
Solution
This article describes how to secure the connection between the FSSO TS-Agent and the FSSO Collector Agent.
 
The FSSO TS-Agent will authenticate against the Collector Agent using TLS with a pre-shared key (PSK). 
This PSK should be known by both client (FSSO TS-Agent) and server (Collector Agent). 
 
In the FSSO-CA configurator tool, check the 'Enable SSL' box and set the 'preshared key'.
It is also possible to configure the SSL port (by default, FSSO-CA will be listening on TCP/8003).
After, select 'Apply' to save the configuration.
 
2024-08-16 10_38_03-TS-Agent_FSSOCA.png

 

In the FSSO TS-Agent configurator tool, select the FSSO CA IP address and port, check the 'Secure connection' box, and set the same pre-shared key used in the FSSO CA configurator tool. Select 'Apply' to save the settings.

 
2024-08-16 10_38_03-TS-Agent_FSSO-CA.png

 

If keepalive messages or login information are not showing under the FSSO Collector Agent -> Show Monitored DCs, it may indicate that the TCP or TLS handshake didn't happen correctly.
 
  1. Check if the FSSO Collector agent is listening on the right TCP port (In the Windows Command line, run 'netstat -ano | findstr <PORT>' and change <PORT> to the configured port).
  2. Check if traffic from the TS-Agent to FSSO CA is allowed via TCP/8003 (default port).
  3. Check a packet capture to confirm the TCP and TLS handshake. A TLS error will be shown during the negotiation if the pre-shared key does not match.

2024-08-16 10_38_03-TS-Agent_TLS.png