GlobalProtect Portals Clientless VPN Tab
- NetworkGlobalProtectPortals<portal-config>Clientless VPN
Clientless VPNtab to configure the GlobalProtect Clientless VPN settings on the portal as described in the following table.
GlobalProtect Portal Clientless Configuration Settings
Clientless VPNto specify general information about the Clientless VPN session:
The IP address or FQDN for the GlobalProtect portal that hosts the web applications landing page. The GlobalProtect Clientless VPN rewrites application URLs with this hostname.
If you use Network Address Translation (NAT) to provide access to the GlobalProtect portal, the IP address or FQDN you enter must match (or resolve to) the NAT IP address for the GlobalProtect portal (the public IP address).
The zone for the Clientless VPN configuration. Security rules defined in this zone control which applications users can access.
The number of
Minutes(range is 60 to 1,440) or
Hours(range is 1 to 24; default is 3) that a clientless SSL VPN session is valid. After the specified time, users must re-authenticate and start a new clientless VPN session.
The number of
Minutes(range is 5 to 1,440; default is 30) or
Hours(range is 1 to 24) that a clientless SSL VPN session can remain idle. If there is no user activity during the specified amount of time, the user must re-authenticate and start a new clientless VPN session.
The maximum numbers of users that can be logged into the portal at the same time (default is 10; range is 1 to no maximum). When the maximum number of users is reached, additional clientless VPN users cannot log in to the portal.
Applications to User Mapping
Addone or more
Applications to User Mappingto match users with published applications. This mapping controls which users or user groups can use a clientless VPN to access applications. You must define the applications and application groups before mapping them to users (Network > GlobalProtect > Clientless Apps and Network > GlobalProtect > Clientless App Groups).
Addindividual users or user groups to which the current application configuration applies. These users have permission to launch the configured applications using a GlobalProtect clientless VPN.
You must configure group mapping (
) before you can select the groups.
Group Mapping Settings
In addition to users and groups, you can specify when these settings apply to the users or groups:
Addindividual applications or application groups to the mapping. The
Source Usersyou included in the configuration can use GlobalProtect clientless VPN to launch the applications you add.
Crypto Settings tab
Select the required minimum and maximum TLS/SSL versions. The higher the TLS version, the more secure the connection. Choices include
Key Exchange Algorithms
Select the supported algorithm types for key exchange. Choices include
RSA, Diffie-Hellman (
DHE), or Elliptic Curve Ephemeral Diffie-Hellman (
Select the supported encryption algorithms.
AES128or higher is recommended.
Select the supported authentication algorithms. Choices are:
SHA256or higher is recommended.
Server Certificate Verification
Enable which actions to take for the following issues that can occur when an application presents a server certificate:
A label of up to 31 characters to identify the proxy server that the GlobalProtect portal uses to access published applications. The name is case-sensitive, must be unique, and can contain only letters, numbers, spaces, hyphens, and underscores.
Add the domains served by the proxy server.
Select to allow the GlobalProtect portal to use the proxy server to access the published applications.
Specify the hostname (or IP address) and port number of the proxy server.
Specify the username and password needed to log in to the proxy server. Enter the password again for verification.
Advanced Settings tab
Rewrite Exclude Domain List
Adddomain names, host names, or IP addresses to the
Rewrite Exclude Domain List. The clientless VPN acts as a reverse proxy and modifies pages returned by the published applications. When a remote users accesses the URL, the requests go through the GlobalProtect portal. In some cases, the application may have pages that do not need to be accessed through the portal. Specify domains that should be excluded from rewrite rules and cannot be rewritten.
Paths are not supported in host and domain names. The wildcard character (*) for host and domain names can only appear at the beginning of the name (for example, *.etrade.com).
Recommended For You
Recommended videos not found.