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

Showing results for 
Show  only  | Search instead for 
Did you mean: 
Palo Alto Networks Approved
Palo Alto Networks Approved
Community Expert Verified
Community Expert Verified

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

L1 Bithead



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.




L1 Bithead

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?

L2 Linker

@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.

L1 Bithead

There will be changes regarding this in 10.1.7

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.

Do you have any idea what the change will be?

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

The LIVEcommunity thanks you for your participation!