GlobalProtect : Network > GlobalProtect > Gateways : GlobalProtect Gateways Agent Tab : Client Settings Tab

Client Settings Tab
•
Network > GlobalProtect > Gateways > <gateway-config> > Agent > <agent-config> > Client Settings
Select the Client Settings tab to configure settings for the virtual network adapter on the endpoint when the GlobalProtect app establishes a tunnel with the gateway.
Note: 
*
Add the specific users or user groups to which this configuration applies.
Note: 
*
You must configure group mapping (Device > User Identification > Group Mapping Settings) before you can select users and groups.
To deploy this configuration to all users, select any from the Source User drop-down. To deploy this configuration only to users with GlobalProtect apps in pre-logon mode, select pre-logon from the Source User drop-down.
Note: 
To deploy this configuration based on the operating system of the endpoint, Add an OS (Android, Chrome, iOS, IoT, Linux, Mac, Windows, WindowsUWP). Alternatively, you can set this value to Any so that configuration deployment is based only on the user or user group and not on the operating system of the endpoint.
Note: 
To deploy this configuration based on user location, Add a source Region or local IP Address (IPv4 and IPv6). To deploy this configuration to all user locations, do not specify a Region or IP Address. You must also leave these fields empty if your users are running GlobalProtect app 4.0 and earlier releases, as this feature is not supported on older GlobalProtect app releases.
Note: 
*
The Source Address match is successful if the location of a connecting user matches either the Region or the IP Address that you configure.
Note: 
•
Generate cookie for authentication override—During the lifetime of the cookie, the agent presents this cookie each time the user authenticates with the gateway.
•
Cookie Lifetime—Specify the hours, days, or weeks that the cookie is valid. The typical lifetime is 24 hours. The ranges are 1–72 hours, 1–52 weeks, or 1–365 days. After the cookie expires, the user must enter login credentials and the gateway subsequently encrypts a new cookie to send to user device.
•
Accept cookie for authentication override—Select this option to configure the gateway to accept authentication using the encrypted cookie. When the agent presents the cookie, the gateway validates that the cookie was encrypted by the gateway before authenticating the user.
•
Certificate to Encrypt/Decrypt Cookie—Select the certificate the gateway uses to use when encrypting and decrypting the cookie.
Note: 
Add a subnet or range of IP addresses to assign to remote users. When the tunnel is established, the GlobalProtect gateway allocates the IP address in this range to connecting devices using the Framed-IP-Address attribute from the authentication server. You can add IPv4 addresses (such as 192.168.74.0/24 and 192.168.75.1-192.168.75.100) or IPv6 addresses (such as 2001:aa::1-2001:aa::10).
You can enable and configure Authentication Server IP Pool only if you enable Retrieve Framed-IP-Address attribute from authentication server.
Note: 
Add a range of IP addresses to assign to remote users. When the tunnel is established, an interface is created on the remote user’s endpoint with an address in this range. You can add IPv4 addresses (such as 192.168.74.0/24 and 192.168.75.1-192.168.75.100) or IPv6 addresses (such as 2001:aa::1-2001:aa::10).
Note: 
Fastpath:
Enable the No direct access to local network setting to reduce risks in untrusted networks such as rogue Wi-Fi access points.
Add routes to include in the VPN tunnel. These are the routes the gateway pushes to the remote users’ endpoint to specify what user endpoints can send through the VPN connection.
Note: 
*
To include all destination subnets or address objects, Include 0.0.0.0/0 and ::/0 as access routes.
Add routes to exclude from the VPN tunnel. These routes are sent through the physical adapter on endpoints rather than through the virtual adapter (the tunnel).
Add the software as a service (SaaS) or public cloud applications that you want to include in the VPN tunnel based on the destination domain and port (optional). These are the applications the gateway pushes to the remote users’ endpoint to specify what user endpoints can send through the VPN connection. ICMP is not included. You can add up to 200 entries to the list.
For example, add the *.office365.com domain to allow all Office 365 traffic to go through the VPN tunnel.
Note: 
Add the software as a service (SaaS) or public cloud applications that you want to exclude from the VPN tunnel based on the destination domain and port (optional). These applications are sent through the physical adapter on endpoints rather than the virtual adapter (the tunnel). You can add up to 200 entries to the list.
For example, add the *.ringcentral.com domain to exclude all RingCentral traffic from the VPN tunnel.
Note: 
Add the complete path of each application process for which you want to include the traffic in your VPN tunnel. These are the applications the gateway pushes to the endpoints of remote users to specify what those user endpoints can send through the VPN connection. You can add up to 200 entries to the list.
For example, add /Application/Safari.app/Contents/MacOS/Safari to allow all Safari-based traffic to go through the VPN tunnel on macOS endpoints.
Add the complete path of each application process for which you want to exclude the traffic from your VPN tunnel. These applications are sent through the physical adapter on endpoints rather than the virtual adapter (the tunnel). You can add up to 200 entries to the list.
•
For Windows endpoints, add %AppData%\Local\RingCentral\SoftPhoneApp\Softphone.exe and %AppData%\Local\RingCentral\SoftPhoneApp\SoftphoneMapiBridge.exe
•
For macOS endpoints, add /Applications/RignCentral for Mac.app/Contents/MacOS/Softphone
GlobalProtect Gateways Agent Tab