Scenario:
[ul]
Customer has no onsite authentication server - everything is google/azure based authAll windows computers have forticlient installedBecause there is no local auth, we can't use FSSO[/ul]
Current Behavior:
[ul]All of the Logs have blank for User or InitiatorIf you look at the FortiClient Monitor you can visually see the currently logged windows user "display name"If a user logs out of windows and a different user logs in, the Forticlient Monitor immediately changes the "display name" to the new user.Only problem - if user logs off windows and no other user logs in the FortiClient Monitor still shows the last user... [/ul]
Feature request:
[ul]If the user doesn't log into Fortigate either directly or through SSO but DOES have FortiClient installed then map/merge the username/IP into the normal logging.Update Forticlient to report "No User" when a user logs off windows[/ul]
Alternately - allow SSO with at least Microsoft Azure Active Directory and Google Enterprise's "Cloud Identity" (my cloud only clients are about 80% AzureAD as their single source of truth for authentication).
Benefit for Fortinet:
[ol]Competitive advantageSell more paid licenses of FortiClientBetter logging data makes Fortigate and Fortinet more useful[/ol]
I hope this feature request is written well enough to be considered.
Thank you
-Neil