LSVPN Satellites unable to sign-in to the portal after upgraded to PAN OS 10.1.2

[yanchen]

Hello,

We have upgraded the PAN OS to the latest version 10.1.2 on 3 of 5 PA firewalls, including the LSVPN portal, and 2 of the satellite firewalls.

The thing is that 2 of the satellite firewalls with the latest PANOS 10.1.2 are unable to log in with the portal.

Auth Method: Satellite Auth Cookie

Error (Portal Side): cookie is invalid and no username, Invalid authentication cookie...

Error (Satellite Side): GlobalProtect Satellite connection to portal failed. Satellite failed to connect to Portal <portal url> due to invalid http response.

The rest of the satellites firewall with the PAN OS(10.0.x) are works as usual. No changes were made on the LSVPN configuration, both of the portal and the satellite.

Please help.

Thanks!

[yanchen]

The problem was solved. 

1. If the portal firewall were upgraded to the PAN-OS 10.1.X, then the satellites should be upgraded to 10.1.x as well, otherwise satellites will fail to log on to the portal with the error: "GlobalProtect Satellite connection to portal failed. Satellite failed to connect to Portal <portal url> due to invalid http response."
2. The enrollment credentials on the satellite side should be re-authenticated after being upgraded to 10.1.x.

[MatthewSabin]

Will 10.0.x clients not be able to get authenticated (or renew certificates) until they're upgraded?

[yanchen]

If the portal running 10.1.x and the satellites are running 10.0.x, then yes, the satellites are unable to get authenticated until they are upgraded to the same version as the portal firewall currently running.

According to the response from Technical support that the PAN-OS version running on all firewalls should be the same as of Portal firewall.

[tigeli]

According to the 10.1 and 10.2 documentation plain serial number is still enough to register devices on the portal but.. it is not. Engineering made undocumented change to the product..  I have no problem with the change itself but it would be nice this would have been documented in the "changes to default behaviour" and in the product documentation itself how to register satellites to the portal.

--cut--

Prior to PAN-OS 10.1, the GP LSVPN Portal would register and authenticate the GP LSVPN Satellite either based on the Serial Number or Authentication Profile (username/password credentials)

To enhance the security for GP LSVPN Satellite registration and authentication, PAN-OS 10.1 added the Satellite Cookie Validation mechanism that uses both the Serial Number and Authentication Profile (username/password credentials) to register and authenticate the GP LSVPN Satellite.

--cut--

[rgafner]

Our customer is facing the same issue starting with 10.1. Unfortunately, the LSVPN authentication cookie used after an initial authentication (username/password) is expiring after 6 months! From an operational view, this creates a lot of headaches. Is there a way to carry out a (controlled) forceful re-authentication to re-new the lifetime of the authentication cookie?

[tigeli]

@rgafner I guess.. no. At least I will be moving away from LSVPN to plain IPsec-tunnels because I'm not going to re-authenticate manually every 6 months for each of the devices we have.

[rgafner]

There will be changes regarding this in 10.1.7

[tigeli]

Or actually.. looked into this. You can use XML API to refresh the portal configuration (haven't tested this though.. :D) with something like:

wget -o/dev/null https://your-firewall-hostname/api/ --post-data='?type=op&cmd=<request><global-protect-satellite><get-portal-config><username>your-username</username><password>your-password</password><satellite>configured-satellite</satellite></get-portal-config></global-protect-satellite></request>&key=your-api-key'

And scheduling that against all of your satellites.

[UrosSustar]

Do you have any idea what the change will be?

[rgafner]

Contact Jason Baucom for details

[UrosSustar]

If you are using LSVPN in combination with ZTP, just forget about it and go directly to static tunnels, since the automated portal authentication won't be possible for some time.

[leitzf]

After a ton of troubleshooting this, I figured out that removing the device serial number from the network > portal > satellites > satellite device list seems to clear the stored cookie on the portal. This then prompts the satellite to re-authenticate using username/password, which you can do via an automated method. I'm running 10.1.8-h2, so your mileage might vary depending on your version

[UrosSustar]

"This then prompts the satellite to re-authenticate using username/password, which you can do via an automated method" - how did you manage to automate U/P?

[leitzf]

There is a CLI command available that you can use to script:
request global-protect-satellite get-portal-config username @username password @password satellite @satellite