topic Re: GlobalProtect App: Portal Connection/Cache Expected Behavior in GlobalProtect Discussions

GlobalProtect App: Portal Connection/Cache Expected Behavior

Y.Tsushima — Wed, 29 Jan 2025 09:47:27 GMT

Hello everyone,

I have questions about the expected behavior of GlobalProtect.

Is it correct to assume that the GlobalProtect App will operate as follows depending on whether the Portal can be connected and whether there is a cache?

(I would appreciate an early response)

1. If the Portal can be connected when the client is started and logged in, if there is a cache, the Config will not be obtained from the Portal and a tunnel connection with the Gateway will be made.

2. If the Portal can be connected when the client is booted and logged in, if there is no cache, the Portal will be connected to, the Config will be re-obtained, and a tunnel connection with the Gateway will be made.

3. If the Portal cannot be connected when the client is booted and logged in, if there is a cache, the cached information will be used to tunnel connection with the Gateway.

4. If the Portal cannot be connected when the client is booted and logged in, if there is no cache, the Portal will not be accessed again and an error will be generated.

Re: GlobalProtect App: Portal Connection/Cache Expected Behavior

JayGolf — Thu, 30 Jan 2025 04:44:36 GMT

Hi @Y.Tsushima ,

GlobalProtect uses cached portal config in 3 scenarios:

Portal is not reachable
Portal's server certificate cannot be verified
"Pre-Logon Tunnel Rename Timeout (sec) (Windows Only)" GlobalProtect Portal Agent's App's setting is set to 0

Under normal circumstances, the Portal connection will be attempted, once connected the Config will be obtained, and a tunnel connection with the Gateway will be made.

If you are having trouble with connectivity and you have successfully logged in previously, the client will use the cached configuration to connect to the last known Gateway. If you have never logged in and cannot connect, the client will be unable to proceed with a Gateway connection and receive an error.

Re: GlobalProtect App: Portal Connection/Cache Expected Behavior

Y.Tsushima — Thu, 30 Jan 2025 05:48:16 GMT

Hello @JayGolf

Thank you for your response.

> If you have never logged in and cannot connect, the client will be unable to proceed with a Gateway connection and receive an error.

I understand that if the portal connection is not possible during client boot and login, if there is no cache (no successful login history), the client will receive an error without retrying to access the portal.

*If I have misunderstood something, I would appreciate it if you could point it out.

One more thing to confirm.

Is my understanding of the following correct?

- If a portal connection is possible when the client starts up or logs in, the cache is not used, but the config is obtained from the portal and a tunnel connection is made to the Gateway.