You are troubleshooting a Syslog-based single sign-on (SSO) issue on FortiAuthenticator, where user authentication is not being correctly mapped from the syslog messages. You need a tool to diagnose…

Question

Options

• ADebug logs > Remote Servers > Syslog Viewer
• BParsing Test Tool
• CDebug logs > SSO Sessions page
• DDebug logs > Single Sign-On > Syslog SSO

• A
  3% (1)
• C
  3% (1)
• D
  93% (28)

Explanation

Context: You're troubleshootingSyslog-based SSOonFortiAuthenticator: Devices (typically firewalls, WLAN controllers, VPN gateways) sendsyslog messagescontaining usernames, IPs, login/logout events. FortiAuthenticator parses those logs using Syslog SSO rulesand injects logon sessions into FSSO for FortiGate. When users are not mapping correctly, you need to see: Did the syslog message arrive? Which matching rule (if any) caught it? What username and IP were extracted? Why was a message ignored or rejected? FortiAuthenticator has a dedicated debug area for this: Debug logs -> Single Sign-On -> Syslog SSO This view shows: Raw syslog lines received Thematching ruleapplied (or "no match") Parsed fields (username, IP, group) Any parsing errors This is exactly the tool designed totroubleshoot and diagnose Syslog SSO issues.

No community discussion yet for this question.