FSSO Authentication in Firewall Policies: Troubleshooting Common Issues
A company uses FSSO (Fortinet Single Sign-On) with a domain controller. Users authenticate to the domain, and the FortiGate retrieves the login events. The firewall policy uses the FSSO group. Some users report that after logging in, they cannot access resources that require authentication. The administrator checks the FSSO status and sees that the FortiGate is receiving login events. What is the most likely cause?
Quick Answer
The answer is that the user's IP address falls outside the source address range defined in the firewall policy. Even when FSSO authentication is functioning correctly and the FortiGate is receiving login events from the domain controller, the policy enforces multiple conditions—not just the FSSO group membership. If the source address object or range in the policy does not include the user’s current IP, the traffic will not match, and access will be denied despite successful authentication. On the Fortinet NSE 4 exam, this scenario tests your understanding that FSSO troubleshooting requires verifying all policy layers, not just the authentication status. A common trap is assuming that seeing “authenticated” in the FSSO monitor guarantees access; in reality, source IP mismatches are a frequent oversight. Remember the mnemonic: “Auth alone won’t let you roam—check the source address to bring you home.”
⚠ Common exam trap
Test-takers frequently assume receiving FSSO login events guarantees policy match, ignoring that the source address condition in the firewall policy is a separate, independent requirement that must also be satisfied.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The user's IP address is not in the source address range of the policy
Even though the FortiGate is receiving FSSO login events, the firewall policy also includes a source address restriction. If the user's IP address falls outside the defined source address range, the policy will not match, and the user will be denied access despite being authenticated via FSSO. The FSSO group membership is only one condition; the source IP must also satisfy the policy's source address criteria.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The user is not a member of the FSSO group
Why it's wrong here
Group membership is evaluated per policy match, and non-membership would deny those users consistently, not intermittently after successful logins. It tempts because wrong group mapping is a frequent FSSO misconfiguration, and it would be correct if the FortiGate showed no events for the affected accounts.
- ✗
The FSSO collector agent is not running
Why it's wrong here
The stem states the FortiGate already receives login events, so the collector agent is functioning; a stopped agent would produce no events at all. It is tempting because a dead collector is a common FSSO fault, and restarting it is the standard fix when the FortiGate shows no logged-on users.
- ✓
The user's IP address is not in the source address range of the policy
Why this is correct
FSSO authenticates the user and populates the group, but the firewall policy still matches on source address; if the workstation's IP falls outside that range, the policy never applies and traffic is denied. This satisfies the stem's symptom of successful login events yet blocked access.
- ✗
The FortiGate is not polling the domain controller
Why it's wrong here
Polling mode is an alternative to collector-agent event forwarding, and the stem confirms events already arrive, so polling is irrelevant here. It tempts because polling failures do stop FSSO updates, but only in deployments configured for DC polling rather than agent-based event retrieval.
Go deeper
Related to this question
About these practice questions
Courseiva writes every NSE4 question from scratch — 773 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on NSE4
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Which THREE conditions must be met for a firewall policy with FSSO authentication to work correctly?
hard- ✓ A.The FortiGate must be able to communicate with the domain controller
- B.The user's IP address must be in the destination address range of the policy
- ✓ C.The user must be a member of a group that is referenced in the firewall policy
- ✓ D.The FSSO collector agent must be running and properly configured
- E.The user must be authenticated to the FortiGate locally
Why A: FSSO (Fortinet Single Sign-On) relies on the FortiGate communicating with the domain controller to retrieve user login events via NetAPI or WMI. Without this communication, the FortiGate cannot map user identities to IP addresses, which is essential for FSSO-based authentication in firewall policies.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This NSE4 practice question is part of Courseiva's free Fortinet certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the NSE4 exam.