Globalprotect MFA with RSA secureID with Radius

Reply

Globalprotect MFA with RSA secureID with Radius

I have a customer who is trying to configure MFA in GP with RSA SecureID server with Radius server profile (Not the MFA profile that was introduced with 8.1).

The first factor should be user name and password and the second factor should be an OTP token.

Both username, passowrd and token should be validated by the RSA server.

I have done the configuration by following the below KB

https://docs.paloaltonetworks.com/globalprotect/8-0/globalprotect-admin/authentication/set-up-two-fa...

 

Now when i try to authenticate GP shows only the first step (Password), and it does not prompt for the OTP.

 

So i need to know if there is a configuration on GP to enable the OTP popup?

Also if am using an email/SMS token, the firewall should send a request first in order for the token to be generated, is there is a way to configure this method in PA?

also is there is a behavior change between 8.0 and 8.1 in the way GP handles MFA with Radius server profile?

L6 Presenter

Re: Globalprotect MFA with RSA secureID with Radius

I think you are getting confused, the KB listed is 2 factor auth, not multi factor.

 

so what is happening is you are logging into the portal with user and password, the portal then generates a cookie to auth you to the gateway.

 

if you need multi factor without using MFA, the best you can do is have seperate auth servers on portal and gateways but unfortunately you are using same radius for both passcode and password...

 

does that make sense?

Re: Globalprotect MFA with RSA secureID with Radius

Yes i tried using seperate auth profiles for portal and gateway and it works.

So you are saying that there is no way to use one authentication profile to do both token and password validation, and this is only available in the new MFA feature?

 

Thanks

L7 Applicator

Re: Globalprotect MFA with RSA secureID with Radius

Hi @AbdallaAbdelkhaliq 

 

What you are asking for is possible. The problem here that GP does not ask for OTP isn't located on the firewall - it is a problem on your RSA server. When your RSA Radius server receives username and password (if the credentials are valid) it needs to reply with an Access-Challenge packet. This way GP would show the OTP prompt. Right now your RADIUS server sends back directly an access-accept packet so the firewall and GP see only a valid authentication without the need to ask for OTP.

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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 Live Community as a whole!

The Live Community thanks you for your participation!