GlobalProtect : Network > GlobalProtect > Portals : GlobalProtect Portals Agent Tab : GlobalProtect Portals Agent App Tab

GlobalProtect Portals Agent App Tab
•
Network > GlobalProtect > Portals > <portal-config> > Agent > <agent-config> > App
Select the App tab to specify how end users interact with the GlobalProtect apps installed on their systems. You can define different app settings for the different GlobalProtect configurations you create. See the GlobalProtect Administrator’s Guide to learn more about the latest updates on the GlobalProtect App Customization settings.
•
On-demand (Manual user-initiated connection)—Users must launch the GlobalProtect app, and then initiate a connection to the portal and enter their GlobalProtect credentials. Use this option primarily for remote access connections.
•
User-logon (Always On)—The GlobalProtect app automatically establishes a connection to the portal after the user logs in to an endpoint. The portal responds by providing the app with the appropriate agent configuration. Subsequently, the app sets up a tunnel to one of the gateways specified in the agent configuration received from the portal.
•
Pre-logon—Pre-logon ensures remote Windows and Mac users are always connected to the corporate network and enables user logon scripts and application of domain policies when the user logs in to the endpoint. Because the endpoint can connect to the corporate network as if it were internal, users can log in with new passwords when their passwords expire or receive help with password recovery if they forget their password. With pre-logon, the GlobalProtect app establishes a VPN tunnel to a GlobalProtect gateway before the user logs in to the endpoint; the endpoint requests authentication by submitting a preinstalled machine certificate to the gateway. Then, on Windows endpoints, the gateway reassigns the VPN tunnel from the pre-logon user to the username that logged in to the endpoint. On Mac endpoints, the app disconnects and creates a new VPN tunnel for the user.
◦
Pre-logon (Always On)—The GlobalProtect app automatically attempts to connect and reconnect to GlobalProtect gateways. Mobile devices don't support pre-logon functionality, and therefore will default to the User-logon (Always On) connect method if this connect method is specified.
◦
Pre-logon then On-demand—Users must launch the GlobalProtect app and then initiate the connection manually. Mobile devices don't support pre-logon functionality, and therefore will default to the On-demand (Manual user-initiated connection) connect method if this connect method is specified.
•
Allow—Allow any user to disable the GlobalProtect app as needed.
•
Disallow—Don't allow end users to disable the GlobalProtect app.
•
Allow with Comment—Allow users to disable the GlobalProtect app on their endpoint but require that they submit their reason for disabling the app.
Note: 
*
The reasons for disconnecting are displayed only if you configure Display the following reasons to disconnect GlobalProtect (Always-on mode). If you did not configure the GlobalProtect app to display the reasons for disconnecting, end users are prompted to provide a reason for disconnecting from the app.
•
Allow with Passcode—Allow users to enter a passcode to disable the GlobalProtect app. This option requires the user to enter and confirm a Passcode value that, like a password, does not display when typed. Typically, administrators provide a passcode to users before unplanned or unanticipated events prevent users from connecting to the network by using the GlobalProtect VPN. You can provide the passcode through email or as a posting on your organization’s website.
•
Allow with Ticket—This option enables a challenge-response mechanism where, after a user attempts to disable GlobalProtect, the endpoint displays an 8-character hexadecimal ticket request number. The user must contact the firewall administrator or support team (preferably by phone for security purposes) to provide this number. From the firewall (Network > GlobalProtect > Portals), the administrator or support person can then click Generate Ticket and enter the ticket Request number to obtain the Ticket number (also an 8-character hexadecimal number). The administrator or support person provides this ticket number to the user, who then enters it into the challenge field to disable the app.
•
Allow—Allow any user to uninstall the GlobalProtect app as needed.
•
Disallow—Don't allow end users to uninstall the GlobalProtect app.
•
Allow with Password—Enforce a password to uninstall the GlobalProtect app. This option requires the user to enter and confirm a password before they can proceed with uninstallation. You can provide the password through email or as a posting on your organization’s website.
•
Disallow—Prevent users from upgrading the app software.
•
Allow Manually—Allow users to manually check for and initiate upgrades by selecting Check Version in the GlobalProtect app.
•
Allow with Prompt (default)—Prompt users when a new version is activated on the firewall and allow users to upgrade their software when it's convenient.
•
Allow Transparently—Automatically upgrade the app software whenever a new version becomes available on the portal.
•
Internal—Automatically upgrade the app software whenever a new version becomes available on the portal, but wait until the endpoint is connected internally to the corporate network. This prevents delays caused by upgrades over low-bandwidth connections.
(Windows, macOS, iOS, Android, and Chrome Only)
•
Yes (default)—Allow any user to sign out from the GlobalProtect app as needed.
•
No—Don't allow end users to sign out from the GlobalProtect app.
Select No to disable single sign-on (SSO). With SSO enabled (default), the GlobalProtect app automatically uses the Windows login credentials to authenticate and then connect to the GlobalProtect portal and gateway. GlobalProtect can also wrap third-party credentials to ensure that Windows users can authenticate and connect even when a third-party credential provider is used to wrap the Windows login credentials.
(Windows 10 or later)
Select No to disable single sign-on (SSO). With SSO enabled (default), the GlobalProtect app automatically uses the macOS login credentials to authenticate and then connect to the GlobalProtect portal and gateway.
(Windows Only)
Select No to keep single sign-on credentials when the user logs out. Select Yes (default) to clear them and force the user to enter credentials upon the next login.
Select No to use only Kerberos authentication. Select Yes (default) to retry authentication by using the default authentication method after a failure to authenticate with Kerberos. This feature is supported for Mac and Windows endpoints only.
(Requires GlobalProtect app 5.2 or later with release version 8284-6139 or later)
If you have configured the GlobalProtect portal to authenticate end users through Security Assertion Markup Language (SAML) authentication, select Yes to enable users to leverage the same login for GlobalProtect with their saved user credentials on the default system browser such as Chrome, Firefox, or Safari to connect to SAML-enabled applications. You must enable this setting if you're using SAML with the Cloud Authentication Service.
If you enable this setting, you must alsochange the pre-deployment settings to enable the default browser on Windows, macOS, Linux, Android, and iOS endpoints to use the default system browser for SAML authentication.
Tip: 
Note: 
Enter the amount of time, in seconds, the GlobalProtect app waits between attempts to reestablish the connection with the last-connected gateway when you enable Automatic Restoration of VPN Connection Timeout. Specify a longer or shorter wait time depending on your network conditions. The range is from 1 to 60 seconds; the default is 5.
(Windows 10 or later and macOS 11 and later only)
•
No—Disables endpoint traffic policy enforcement. This is the default setting.
•
TCP/UDP Traffic Based on Tunnel IP Address Type—Enables endpoint traffic policy enforcement for TCP/UDP traffic. This feature is enabled for traffic based on the tunnel IP address type. If the tunnel is IPv4, this feature applies only to IPv4 traffic. If the tunnel is IPv6, this features applies only to IPv6 traffic.
•
All TCP/UDP Traffic—Enables endpoint traffic policy enforcement for all TCP/UDP traffic regardless of the tunnel IP address type. If the tunnel IP address type is IPv4, endpoint traffic policy enforcement applies to all TCP/UDP (IPv4 or IPv6) traffic. If the tunnel IP address type is IPv6, endpoint traffic policy enforcement applies to all TCP/UDP (IPv4 or IPv6) traffic.
•
All Traffic—Enables endpoint traffic policy enforcement for all TCP, UDP, ICMP, and all other protocols regardless of the tunnel IP address type.
Select Yes to force all network traffic to traverse a GlobalProtect tunnel. Select No (default) if GlobalProtect is not required for network access and users can still access the internet even when GlobalProtect is disabled or disconnected.
To provide instructions to users before traffic is blocked, configure a Traffic Blocking Notification Message and optionally specify when to display the message (Traffic Blocking Notification Delay).
To permit traffic required to establish a connection with a captive portal, specify a Captive Portal Exception Timeout. The user must authenticate with the portal before the timeout expires. To provide additional instructions, configure a Captive Portal Detection Message and optionally specify when to display the message (Captive Portal Notification Delay).
Note: 
*
In most cases, use the default selection No. Selecting Yes blocks all network traffic to and from the endpoint until the app connects to an internal gateway inside the enterprise or to an external gateway outside the enterprise network.
(Windows and macOS 10.15.4 or later)
CAUTION:
Due to a recent change in macOS, enforcing GlobalProtect connections with FQDN exclusions for multiple network extensions being loaded at a time does not work in certain situations, such as in environments where DnsClient.Net, GlobalProtect with the Allow traffic to specified FQDN when Enforce GlobalProtect Connection for Network Access is enabled and GlobalProtect Connection is not established setting enabled, and Cortex XDR are running.
Specifies whether a message appears when GlobalProtect is required for network access. Select No to disable the message. Select Yes to enable the message (GlobalProtect displays the message when GlobalProtect is disconnected but detects that the network is reachable.)
Select No to always display traffic blocking notifications. By default the value is set to Yes meaning users are permitted to dismiss the notifications.
Specifies whether a message appears when GlobalProtect detects a captive portal. Select Yes to display the message. Select No (default) to suppress the message (GlobalProtect does not display a message when GlobalProtect detects a captive portal).
CAUTION: 
Note: 
•
User—Authenticate by using the certificate that is local to the user’s account.
•
Machine—Authenticate by using the certificate that is local to the endpoint. This certificate applies to all the user accounts permitted to use the endpoint.
•
User and machine (default)—Authenticate by using the user certificate and the machine certificate.
(Windows and macOS only)
(Windows Only)
Select Yes to retain the connection when a user removes a smart card containing a client certificate. Select No (default) to terminate the connection when a user removes a smart card.
Select No to restrict the user interface on the app to the basic, minimum view (enabled by default).
Select No to force the Welcome Page to appear each time a user initiates a connection. This restriction prevents a user from dismissing important information, such as terms and conditions that may be required by your organization to maintain compliance.
Select Yes to require the end user to accept terms of use to comply with corporate policies and to see a page to review your company’s terms of service before connecting to GlobalProtect.
Before you set this option to Yes, you must configure the GlobalProtect Welcome page through Network > GlobalProtect > Portals > <portal_config > General).
Select No to prevent users from manually initiating a network rediscovery.
Select No to prevent users from manually triggering resubmission of the latest HIP.
Select No to disable the Portal field on the Home tab in the GlobalProtect app. However, because the user will then be unable to specify a portal to which to connect, you must supply the default portal address in the Windows registry or Mac plist:
•
Windows registry—HKEY_LOCAL_MACHINE\SOFTWARE\PaloAlto Networks\GlobalProtect\PanSetup with key Portal
•
Mac plist—/Library/Preferences/com.paloaltonetworks.GlobalProtect.pansetup.plist with key Portal
Select No to prevent the app from establishing a connection with the portal if the portal certificate is not valid.
Select No to hide the GlobalProtect icon on the endpoint. If the icon is hidden, users cannot perform certain tasks, such as viewing troubleshooting information, changing passwords, rediscovering the network, or performing an on-demand connection. However, HIP notification messages, login prompts, and certificate dialogs do display when user interaction is necessary.
(Windows only)
To enable GlobalProtect to preserve the existing VPN tunnel after users log out of their endpoint, specify a Preserve Tunnel on User Logoff Timeout value (range is 0 to 600 seconds; default is 0 seconds). If you accept the default value of 0, GlobalProtect does not preserve the tunnel following user logout.
(LDAP Authentication Only)
Specify the amount of time (in hours) during which you want the GlobalProtect app to Automatically Use SSL When IPSec Is Unreliable (range is 0-168 hours). If you configure this option, the GlobalProtect app does not attempt to establish an IPSec tunnel during the specified time period. This timer initiates each time an IPSec tunnel goes down due to a tunnel keepalive timeout.
If you accept the default value of 0, the app does not fall back to establishing an SSL tunnel if it can establish an IPSec tunnel successfully. It falls back to establishing an SSL tunnel only when the IPSec tunnel cannot be established.
Select No if you do not want users to see a notification message indicating that their connection has changed from IPSec to SSL. By default users will be notified.
Select Yes if you want users to be able to choose to use SSL instead of IPSec.
Select Yes to enable the GlobalProtect app to validate the server certificate of the internal gateways in addition to performing a reverse DNS lookup of the internal host during internal host detection.
Select No (default) for GlobalProtect app to perform internal host detection without validating the server certificate of the internal gateways.
Select Yes to allow users to extend the login lifetime session of the GlobalProtect app before it expires to prevent abrupt app session logout.
Select No (default) if you do not want users to be able to extend the login lifetime session of the GlobalProtect app before it expires.
Set the HIP Remediation Process Timeout (sec) to configure a timeout period during which the GlobalProtect app can run a HIP process remediation script if it fails a HIP process check.
Specify the Enhanced Split Tunnel Client Certificate Public Key that the endpoint can use to connect to the web server hosting the split tunnel configuration file.
Specify the HIP Process Remediation Retry count to enable the HIP process remediation retry feature.
Specify whether to enable split-tunnel domain and/or split DNS feature for the traffic based on the exclude or include domains configured on the GlobalProtect gateway under Network > GlobalProtect > Gateway > Agent > Client Setting > (Client Config) > Split Tunnel > Domain and Application.
Network Traffic Only—Select this option to enable only split-tunnel domain for the traffic as per include or exclude domains configured on the GlobalProtect gateway under Network > GlobalProtect > Gateway > Agent > Client Setting > (Client Config) > Split Tunnel > Domain and Application.
Both Network Traffic and DNS—Select this option to enable both split-tunnel domain and split DNS for the traffic as per include or exclude domains configured on the GlobalProtect gateway under Network > GlobalProtect > Gateway > Agent > Client Setting > (Client Config) > Split Tunnel > Domain and Application.
(GlobalProtect 4.0.3 and later releases) Configure the DNS resolution preferences when the GlobalProtect tunnel is connected on Windows endpoints:
•
Select Yes (default) to enable the GlobalProtect app to allow Windows endpoints to resolve all DNS queries with the DNS servers you configure on the gateway instead of allowing the endpoint to send some DNS queries to the DNS servers set on the physical adapter.
•
Select No to allow Windows endpoints to send DNS queries to the DNS server set on the physical adapter if the initial query to the DNS server configured on the gateway is not resolved. This option retains the native Windows behavior to query all DNS servers on all adapters recursively but can result in long wait times to resolve some DNS queries.
By default, the Agent Mode for Prisma Access is set to Tunnel mode, which means that the GlobalProtect app establishes a tunnel to GlobalProtect to secure internet and private app access, based on any split-tunnel rules you have defined. If you want to enable explicit proxy functionality in the GlobalProtect app to enable always-on security for internet traffic while providing on-demand access to private apps through GlobalProtect or a third-party VPN, you can configure one of the following agent modes:
Select Proxy to enable the GlobalProtect app to proxy traffic to Prisma Access based on forwarding rules defined in the PAC file. You can then secure access to your private apps using a third-party VPN.
Select Tunnel and Proxy to enable the GlobalProtect app to send the internet traffic to the explicit proxy based on rules you define in the PAC file. For the remaining traffic, the GlobalProtect app uses the split tunneling rules you have defined to determine which traffic to send through the tunnel.
(Windows Only) (Deprecated)
(GlobalProtect 4.0.2 and earlier releases) Configure the DNS server preferences for the GlobalProtect tunnel:
•
Select No (default) to allow Windows endpoints to send DNS queries to the DNS server set on the physical adapter if the initial query to the DNS server configured on the gateway is not resolved. This option retains the native Windows behavior to query all DNS servers on all adapters recursively but can result in long wait times to resolve some DNS queries.
•
Select Yes to enable Windows endpoints to resolve all DNS queries with the DNS servers you configure on the gateway instead of the DNS servers set on the physical adapter on the endpoint. When you enable this option, GlobalProtect strictly enforces the gateway DNS settings and overrides the static settings for all physical adapters.
Note: 
*
When this setting is enabled, (set to Yes) GlobalProtect can fail to restore the previously saved DNS settings, and as a result, can prevent the endpoint from resolving DNS queries. This feature is deprecated and is replaced with an improved implementation so that this scenario does not occur. If you were previously using this feature we recommend upgrading to GlobalProtect app 4.0.3 or a later release.
To configure DNS settings for GlobalProtect app 4.0.3 and later releases, use the Resolve All FQDNs Using DNS Servers Assigned by the Tunnel option.
Select Yes to push the URL for your proxy auto-configuration (PAC) files from the GlobalProtect app to your endpoints.
(Windows only)
Select No to auto-detect the proxy for the portal connection and use that proxy for subsequent connections. Select Yes (default) to auto-detect the proxy at every connection.
Set Up Tunnel Over Proxy (Windows & Mac Only)
Specify whether GlobalProtect must use or bypass proxies. Select No to require GlobalProtect to bypass proxies. Select Yes to require GlobalProtect to use proxies. Based on the GlobalProtect proxy use, endpoint OS, and tunnel type, network traffic will behave differently.
(Windows Only)
Select No to prevent the GlobalProtect app from sending HIP data when the status of the Windows Security Center (WSC) changes. Select Yes (default) to immediately send HIP data when the status of the WSC changes.
To support multi-factor authentication (MFA), a GlobalProtect endpoint must receive and acknowledge UDP prompts that are inbound from the gateway. Select Yes to enable a GlobalProtect endpoint to receive and acknowledge the prompt. Select No (default) for GlobalProtect to block UDP prompts from the gateway.
Specifies the preferred protocol for GlobalProtect endpoint communications. Select No to change the preferred protocol to IPv4.Select Yes (default) to make IPv6 the preferred connection a dual-stack environment.
Select Yes to enable the GlobalProtect app to send the gateway selection criteria logs to the firewall. The default is No. The app does not send the enhanced logs for the gateway selection criteria to the firewall.
Select Yes to enable the GlobalProtect app to display the Report an Issue option to allow end users to send the troubleshooting and diagnostic logs directly to Strata Logging Service. You must configure the Strata Logging Service certificate that is pushed from the portal as a client certificate to display the Report an Issue option. This certificate is used for the client to authenticate to Strata Logging Service when sending the logs. When this setting is set to No (default), the GlobalProtect app will not display the Report an Issue option and end users cannot send the troubleshooting and diagnostic logs to Strata Logging Service.
Select Yes if you want users to see notifications whenever the ADEM agent is updated.
Enter up to ten HTTPS-based destination URLs to initiate performance tests for probing. These diagnostic tests are only run if you chose to Enable Autonomous DEM and GlobalProtect App Log Collection for Troubleshooting. The destination URLs you enter can be IP addresses or fully qualified domain names (for example, https://10.10.10.10/resource.html, https://webserver/file.pdf, or https://google.com).
•
Select Install and user can enable/disable agent from GlobalProtect to install the ADEM endpoint agent during the GlobalProtect app installation, and allow end users to enable or disable user experience tests from the GlobalProtect app.
•
Select Install and user cannot enable/disable agent from GlobalProtect to install the ADEM endpoint agent during the GlobalProtect app installation, and not allow end users to enable or disable user experience tests from the GlobalProtect app.
•
Select Do Not Install (default) to not install the ADEM endpoint agent during the GlobalProtect app installation.
Select Yes to automatically display the GlobalProtect status panel when users establish a connection for the first time. Select No to suppress the GlobalProtect status panel when users establish a connection for the first time.
(Windows 10 or later and macOS)
Select Yes to enable the GlobalProtect app to continue to display the status panel on the screen when end users are entering their credentials.
Enter and then confirm a passcode if the setting for Allow User to Disable GlobalProtect App is Allow with Passcode. Treat this passcode like a password—record it and store it in a secure place. You can distribute the passcode to new GlobalProtect users by email or post it in a support area of your company website.
Fastpath: 
Fastpath: 
GlobalProtect Portals Agent Tab