I have looked at the different support documents and previous discussions but have not gotten much wiser.
I need to have a handful of users connect to GlobalProtect with TOTP as the second authentication factor. Since the number of users are so low, they can either live on our LDAP service (preferred) or as local users. The TOTP is to be verified by existing RADIUS.
On existing solutions, such as Cisco ASA (AnyConnect), the authentication flow is as follows for on demand VPN:
a) user provides username, password and one time password on login screen
b) username and password is used to authenticate against LDAP
c) username and one time password is sent to RADIUS for match against the TOTP backend
d) user is logged in
On PaloAlto I would perhaps expect the flow to be something like:
a) user provides username and password to GP portal
b) username and password is authenticated against LDAP (or local user database)
c) gp portal checks for valid authentication cookie, if valid go last step
d) ask user for one time password
e) username and one time password is sent to RADIUS for match again TOTP backend
f) set authentication cookie
g) authentication override allows user to connect to GP gateway using authentication cookie
Is it possible to set up something like this, or do we need to build a completely different RADIUS TOTP setup just for GP?
Same here minus the RADIUS server. If I avoid using two-factor authentication with GlobalProtect to authenticate to the gateway or portal, it should be possible to use GlobalProtect to notify the user about an authentication policy match (UDP message), a Multi Factor Authentication server profile would be sufficient, yes? Specifically, I would like to know how this would work with Google Authenticator.
UPDATE: TAC response.
For remote user authentication to GlobalProtect portals and gateways, the firewall integrates with MFA vendors using RADIUS and SAML only. As of now, The Google authenticator app is not supported by Palo Alto for multi-factor authentication. Supported MFA vendors are Okta, PingID, RSA token, DUO. Below document explains about the Multi Factor authentication in detail.
Hi @EStangeland ,
Here's the compatibility matrix for MFA vendor support:
Here are some updated links to replace the old ones:
For those organizations that need to configure GlobalProtect with Google Authenticator, there are a couple of options.
I have not configured Google MFA, but I have done these solutions with other products. I found the links through Google.
I tried SAML against Microsoft 365 in lab. It works.
But if you need multi tenant, and at same time avoid having to create one GP gateway per tenant, you still have a problem.
I did some experiments using https://login.microsoftonline.com/common/saml2 - but still without finding a working setup for multi tenant.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!