Technical Tip: How to prevent FSSO RDP logon from overriding existing user identity (polling mode)
| Description | This article describes how RDP logons in environments using FortiGate with FSSO can update the IP-to-user mapping and change the active user identity, potentially impacting group-based security or web-filtering policies. This behavior is expected when FSSO operates in Windows Event Log polling mode without logon filtering, as both interactive and RDP logon events are processed. |
| Scope | FortiAuthenticator |
| Solution | Problem statement (what is happening):
Every successful RDP logon (Event ID 4624) is treated as a valid user login and mapped to the source IP. s a result:
Confirm the FSSO method in use:
Before applying any configuration changes, the FSSO method in use must be identified.
In FortiAuthenticator, navigate to Fortinet SSO -> Settings -> Methods.
If the configured FSSO method uses the Collector Agent, the behavior and mitigation options differ from those described in this article. For Collector Agent deployments, two supported approaches are available:
The Ignore User List in the Collector Agent GUI can be used to exclude specific user accounts from FSSO processing. Logon events generated by these users are ignored and do not update the IP-to-user mapping.
See Technical Tip: How and why to use the 'Ignore User List' option in FSSO Collector Agent.
The RDP logon override feature in the Collector Agent GUI allows control over how RDP logon events affect existing user mappings, preventing remote logons from unintentionally replacing the active user identity.
See Technical Tip: FSSO RDP logon override.
Windows Event Log polling:
If the configured FSSO method is Windows Event Log polling, the behavior described in this article applies.
Excluding users or groups from FSSO polling events:
To prevent specific user or group logon events from being processed by FSSO when using Windows Event Log polling, exclusions must be configured using SSO Users / SSO Groups and Fine-grained Controls, as outlined in the following steps.
Step 1: Define users or groups for exclusion.
Or:
Create or import the Active Directory user(s) or group(s) whose logon events should be excluded from FSSO polling.
Once at least one user or group is defined, the related filtering and fine-grained control options become available.
Navigate to: Fortinet SSO -> Filtering -> Fine-grained Controls.
Select the appropriate tab at the top:
Select the previously created or imported user(s) or group(s).
Choose Exclude from SSO.
Save the configuration.
 
This configuration instructs FortiAuthenticator to ignore logon events generated by the selected users or groups, preventing those events from updating the IP-to-user mapping. 
Resulting behavior: Excluded user or group logon events are ignored by FSSO, preventing RDP or secondary logons from overriding the existing IP-to-user mapping. Group-based firewall and web-filtering policies continue to evaluate the intended user.
Note: This approach should be applied selectively and is recommended for shared workstations, jump servers, and administrative RDP access, where Fine-grained Controls provide precise and supported identity filtering in Windows Event Log polling mode.
Related documents: Technical Tip: How and why to use the 'Ignore User List' option in FSSO Collector Agent |




