Question 530
At a financial services branch, a test team is validating a change after this incident: A contractor's browser proxy authentication loops because SAML redirect URLs retain an old domain after a secure web gateway hostname change. What evidence most directly verifies the intended outcome?
Explanation
Correct Answer
Browser-only sign-in completes without redirect loops and the protected web session is logged. This evidence directly tests the intended corrective action: Correct the approved agentless proxy SAML redirect and reply URLs at the application and identity provider. It confirms the failure mechanism—Federation callbacks must match the actual hosted service endpoint.—has been addressed in the actual affected flow.
Incorrect Answers
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 approved agentless proxy SAML redirect and reply URLs at the application and identity provider.—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 approved agentless proxy SAML redirect and reply URLs at the application and identity provider.—worked.
Members of separate test groups match their intended access restrictions after SSO. This would verify resolution of a different case: A FortiSASE SAML integration accepts users but places everyone into a default policy because role and group assertions are missing from the issued claim. It does not show that the reported issue was fixed or that its intended action—Correct the approved agentless proxy SAML redirect and reply URLs at the application and identity provider.—worked.