12-02-2021 06:43 AM
We recently implemented Duo Multi-Factor Authentication (MFA) and have configured GlobalProtect to use Duo's SSO service (which in turn Duo uses Azure AD for authenticating the user). We are using SAML for authentication, so when the user clicks 'Connect', GlobalProtect does the portal connection first and is told by the Palo Alto to open it's embedded browser, call the Duo SSO web service, which in turn calls the Azure AD SSO web service, collects and validates the user's username/password, then passes GP back to Duo to prompt for MFA which once approved is passed back to the Palo Alto to allow GP to connect to the portal. The process is then repeated for the gateway, although we have the portal configured to use cookies so that the user doesn't get prompted for MFA twice. This works fine when we are using Connect AFTER Logon (user logs into Windows first and then connects the VPN).
The issue we are having is with Connect BEFORE Logon. With GlobalProtect 5.2.8, the browser window appears to be stuck between Azure AD and Duo MFA. We see the Azure AD credentials authenticate succesfully and the Microsoft prompt goes away (so that must be working), and we briefly see the Duo MFA Universal Prompt attempt to open, but it flashes on the screen for a second and then the GP window just shows a blank window. In the logs, the last thing we see GP do is open two Duo web service URLs. Then nothing until we cancel GlobalProtect. NOTE: I just tried 5.2.9 and it actually gets stuck earlier in the process, just after the user enters their Azure AD password. It just hands on the "enter password" screen like it never gets back a "succesful". In the 5.2.9 logs, i see the URL for the Azure AD login page, with the word BLOCK in front of it. Does that make any sense?
Any suggestions on how to troubleshoot this? Is it the cookies maybe?
