FSSO with Fortigate

Hi Experts,

I want to use FSSO with my Fortigate and I want to use webfilters for my departments.
All is setup and working.

But something is really strange and I get a lot of emails from FORIGATE about AD AUTHENTICATION FAILED.

I Have one Webfilter, it blocks just one site the rest is open.
But why I get this errors ?

Message meets Alert condition
date=2015-05-06 time=13:44:16 devname=FORTI device_id=FGxx log_id=0106043013 type=event subtype=auth  pri=notice vd="root" src= dst= proto=6 policyid=70 user="N/A" adgroup="N/A" ui="(" action=FSSO-auth status=failure reason="none" msg="AD group  user  failed in authentication" 

Open in new window

The responding security group has all my admins as members.
And when I login to the server with my admin,  the internet is reachable and the blocked site is correct.

When all sites are allowed, why I get so much alerts from FORTIGATE ?
Eprs_AdminSystem ArchitectAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

btanExec ConsultantCommented:
I supposed you have followed the recommended steps

may be related, just to make sure these are triggering the thunks of alerts.
 from kb, it also shared collector agent cannot connect to user machine but not able to connect to it..include remote registry to be enabled in host etc
there are other considerations
Workstation Verify Interval - Interval after which FSSO Agent Checks if user is still logged on to domain. If we set it to 0 it will disable the check. This might be the reason why we are not getting any LOGOFF events in Fortigate LOGS. We can set it to 60 minutes.
Dead Entry timeout Interval – If a user disconnects from Network without logging off then FSSO cannot do a verify check. This is the interval after which FSSO Agent will purge the login information of all those users whose IP is not reachable. Setting this value to zero will disable the check. We can set it to 720 minutes.
IP Address Change Verify – FSSO Agent periodically cheeks the IP Address of logged in users and updates the IP Address in case of change. This check will be disabled if set to 0.
below are some commands useful to Test FSSO on Fortigate:
diag debug authd fsso server-status
diag debug authd fsso list

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Eprs_AdminSystem ArchitectAuthor Commented:
Great hints thank you.
These test commands just for the FORTIGATE command line ?
Is it a problem to start them during the day ?
Eprs_AdminSystem ArchitectAuthor Commented:
Another issue is this reg key:

 "Regedit", edit HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers, set permissions for winreg and allow Local Service with R and W.

On my workstation the permission is just Read. Write is not possible just Write Owner.
What can I change here and is it really necessarry ?
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

btanExec ConsultantCommented:
the debug commands are for FG. It should be fine running those two command since it is supposed to just show connectivity status unlike cases to collect very detailed running stats or sniffing log traffic packet that can take up to ard 10% addition of FG resources. But of course if the CPU of the FG is pretty high close to 100% suggest you do it later (otherwise it can drop more packets or sessions) but should still do it during "non-peak" office hours (like lunch time) as that is when still user are connecting or stay connected etc...

For the registry, as long as "Local Service" user account has Read should be good as per in the MS kb...

If Fortinet Server Authentication Extension (FSAE) is also used in DC which works closely with FSSO, do also check out this. The steps to check is rather similar..
Eprs_AdminSystem ArchitectAuthor Commented:
Thanks for the link and I have done it like this.
Eprs_AdminSystem ArchitectAuthor Commented:
The debug commands also working on my fortigate, just some commands differ ea little bit.
btanExec ConsultantCommented:
thanks for sharing and if poss can share more on the "little' differences to benefit the community to learn from your experience too :)
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Hardware Firewalls

From novice to tech pro — start learning today.