GlobalProtect 6.3.3-h15 Linux Known Issues
Focus
Focus
GlobalProtect

GlobalProtect 6.3.3-h15 Linux Known Issues

Table of Contents

GlobalProtect 6.3.3-h15 Linux Known Issues

Lists the known issues in GlobalProtect 6.3.3-h15 Linux.
Issue ID
Description
GPC-27949
On GlobalProtect™ app for Linux endpoints, when a gateway configured for SAML authentication with the default browser requires re-authentication—for example, after the gateway session lifetime expires—and the SAML login is not completed in the browser, the app does not time out the pending authentication. The app continues to display Connecting and does not return to a disconnected state, report an authentication timeout, or retry the connection on its own. Selecting Connect has no effect while the app is in this state. This condition is most likely to occur when a gateway re-authentication begins while the user is away from the endpoint and the SAML login prompt is left unattended.
Workaround: Restart the GlobalProtect service on the endpoint by running systemctl restart gpd.service, and then reconnect.
GPC-27889
On GlobalProtect (GP) app version 6.3.3-699, when the GlobalProtect portal authentication profile is configured for "Client Certificate OR Cloud Identity Engine" and a PKCS#12 client certificate fails to import because its issuer is not in the acceptable Certificate Authority (CA) list, the GlobalProtect user interface (UI) stops responding at the certificate dialog. The Cloud Identity Engine (CIE) pre-login process does not initiate, no browser window opens for authentication, and no error message is displayed. Consequently, a GlobalProtect tunnel is not established.
GPC-27877
When a GlobalProtect client machine experiences an unclean shutdown while the GlobalProtect app is performing a configuration write (such as during a disconnect, reconnect, or portal configuration refresh), the GlobalProtect client cannot connect to any portal. Workaround: Manually remove the zero-byte GlobalProtect configuration and certificate files from the client machine. After these files are removed, the GlobalProtect client can connect successfully.