topic Re: PA 7.0, GP and RSA-ID double authentication in General Topics

PA 7.0, GP and RSA-ID double authentication

nikoo — Tue, 07 Mar 2017 12:02:03 GMT

Hi,

There is a deployment with RSA-ID as OTP and GP as VPN client (3.1 or 3.0). PAN-OS version 7.0.14.

After the recent upgrade from 6.x to 7.x an issue showed up - when authenticating from GP - login information is asked twice.

This seems like a known issue:

https://community.rsa.com/docs/DOC-46969

I've adjusted the PA settings according to this: https://live.paloaltonetworks.com/t5/Management-Articles/GlobalProtect-with-RSA-OTP-behavior-change-from-PAN-OS-7-0-1-or/ta-p/65176

But that did not help, double authentication is still asked every time. GP client was reinstalled and local data cleared.

Basically, after investigation of PA logs, it can be seen that when client connects, he's asked for the username and passcode (PIN+Code). After that the connection is accepted by RADIUS (RSA) and instantly there is a new request made by PA in a blink of an eye and that is rejected. Due to that a new login is required - after that connection succeeds, connection is accepted and VPN connection established.

Is this really how it should work and there is no way around it?

Re: PA 7.0, GP and RSA-ID double authentication

nikoo — Thu, 09 Mar 2017 08:18:21 GMT

A little bump, maybe still someone has some insight?

Re: PA 7.0, GP and RSA-ID double authentication

VinceM — Thu, 09 Mar 2017 10:29:54 GMT

Hi,

OTP is Ine Time Password .. but for GP, you need one auth onportal and one on gateway 🙂 Mean you need Two Time Password 🙂

or you just have to confogure on partial cookie generation and allow you rgatewy to use this cookie for authentication.

https://www.paloaltonetworks.com.br/documentation/71/globalprotect/globalprotect-admin-guide/set-up-the-globalprotect-infrastructure/set-up-two-factor-authentication.html

Hope help.

Re: PA 7.0, GP and RSA-ID double authentication

nikoo — Wed, 15 Mar 2017 08:09:54 GMT

Yea, it should be OTP, but turned out as TTP. 🙂

Well, fine, will upgrade to 7.1 when possible although there was a cookie to feed for the client in 7.0 as well, but that did not do the trick. We'll see if this will make it better.