Question 470
Following remediation at a research campus, engineers revisit: A remote user enters a correct password but FortiSASE authentication against a central LDAP directory fails because the configured base DN excludes that organizational unit. Which observation would BEST prove the specific issue is resolved?
Explanation
Correct Answer
A user in the previously omitted OU is found and permitted according to group rules. This evidence directly tests the intended corrective action: Correct the supported LDAP search base and bind scope while preserving authorized authentication constraints. It confirms the failure mechanism—Directory lookups are restricted by configured search base and binding scope.—has been addressed in the actual affected flow.
Incorrect Answers
The employee device appears as enrolled and traffic uses the expected FortiSASE connection. This would verify resolution of a different case: Remote employees are instructed to use FortiSASE agent-based protection but no FortiClient installation or managed registration has been completed. It does not show that the reported issue was fixed or that its intended action—Correct the supported LDAP search base and bind scope while preserving authorized authentication constraints.—worked.
A test user's RADIUS request succeeds with expected acceptance and group behavior. This would verify resolution of a different case: A FortiSASE tenant uses RADIUS for user authentication but the RADIUS shared secret was changed on FortiAuthenticator only. It does not show that the reported issue was fixed or that its intended action—Correct the supported LDAP search base and bind scope while preserving authorized authentication constraints.—worked.
A test user connects to an approved low-latency PoP and receives the right group policy. This would verify resolution of a different case: An endpoint registers successfully but the FortiClient service profile applies to the wrong geographic user group, routing employees through a distant PoP. It does not show that the reported issue was fixed or that its intended action—Correct the supported LDAP search base and bind scope while preserving authorized authentication constraints.—worked.