Feature Request: Fortigate logging to add "Username" based Forticlient if no direct login

[NeilG]

Scenario:

[ul]

Customer has no onsite authentication server - everything is google/azure based auth

All windows computers have forticlient installed

Because there is no local auth, we can't use FSSO[/ul]

Current Behavior:

[ul]

All of the Logs have blank for User or Initiator

If 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 advantage

Sell more paid licenses of FortiClient

Better logging data makes Fortigate and Fortinet more useful[/ol]

I hope this feature request is written well enough to be considered.

Thank you

-Neil