Question 490
An operations review at a university network has corrected: A FortiSASE tenant uses RADIUS for user authentication but the RADIUS shared secret was changed on FortiAuthenticator only. Which observation specifically confirms success?
Explanation
Correct Answer
A test user's RADIUS request succeeds with expected acceptance and group behavior. This evidence directly tests the intended corrective action: Synchronize the approved RADIUS client/server shared secret and test authentication exchanges. It confirms the failure mechanism—RADIUS authentication fails when client and server trust secrets no longer match.—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—Synchronize the approved RADIUS client/server shared secret and test authentication exchanges.—worked.
Connection status shows the FortiSASE service and security traffic enters the expected PoP. This would verify resolution of a different case: FortiClient is installed but its VPN connection uses a direct on-premises FortiGate tunnel instead of the intended FortiSASE service. It does not show that the reported issue was fixed or that its intended action—Synchronize the approved RADIUS client/server shared secret and test authentication exchanges.—worked.
Browser-only sign-in completes without redirect loops and the protected web session is logged. This would verify resolution of a different case: A contractor's browser proxy authentication loops because SAML redirect URLs retain an old domain after a secure web gateway hostname change. It does not show that the reported issue was fixed or that its intended action—Synchronize the approved RADIUS client/server shared secret and test authentication exchanges.—worked.