Define the GlobalProtect Client Authentication Configurations

Each GlobalProtect client authentication configuration specifies the settings that enable the user to authenticate with the GlobalProtect portal. You can customize the settings for each OS or you can configure the settings to apply to all endpoints. For example, you can configure Android users to use RADIUS authentication and Windows users to use LDAP authentication. You can also customize client authentication for users who access the portal from a web browser (to download the GlobalProtect app) or for third-party IPsec VPN (X-Auth) access to GlobalProtect gateways.
  1. Set Up Access to the GlobalProtect Portal.
  2. Specify how the portal authenticates users.
    You can configure the GlobalProtect portal to authenticate users through a local user database or an external authentication service, such as LDAP, Kerberos, TACACS+, SAML, or RADIUS (including OTP). If you have not yet set up the authentication profiles and/or certificate profiles, see Authentication for instructions.
    On the GlobalProtect Portal Configuration dialog (NetworkGlobalProtectPortals<portal-config>), select Authentication to Add a new Client Authentication configuration with the following settings:
    • Enter a Name to identify the client authentication configuration.
    • Specify the endpoints to which you want to deploy this configuration. By default, the configuration applies to all endpoints. You can apply the configuration to endpoints running a specific OS or to endpoints that access the portal from a web Browser with the intent of downloading the GlobalProtect app or creating a new client authentication configuration specifically for GlobalProtect Clientless VPN.
    • Select or add an Authentication Profile for authenticating endpoints that try to access the gateway.
    • (Optional) Enter a custom Username Label for GlobalProtect portal login (for example, Email Address (username@domain).
    • (Optional) Enter a custom Password Label for GlobalProtect portal login (for example, Passcode for two-factor, token-based authentication).
    • (Optional) Enter an Authentication Message to help end users understand which credentials to use when logging in. The message can be up to 256 characters in length (default is Enterlogin credentials).
  3. Arrange the client authentication configurations with OS-specific configurations at the top of the list, and configurations that apply to Any OS at the bottom of the list (NetworkGlobalProtectPortals<portal-config>Authentication). As with security rule evaluation, the portal looks for a match starting from the top of the list. When it finds a match, it delivers the corresponding configuration to the app.
    • To move a client authentication configuration up on the list of configurations, select the configuration and click Move Up.
    • To move a client authentication configuration down on the list of configurations, select the configuration and click Move Down.
  4. (Optional) To enable two-factor authentication using an authentication profile and a certificate profile, configure both in this portal configuration.
    The portal must authenticate the endpoint by using both methods before the user can gain access.
    (Chrome only) If you configure the portal to use client certificates and LDAP for two-factor authentication, Chromebooks that run Chrome OS 47 or later versions encounter excessive prompts to select the client certificate. To prevent excessive prompts, configure a policy to specify the client certificate in the Google Admin console and then deploy that policy to your managed Chromebooks:
    1. Log in to the Google Admin console and select Device managementChrome managementUser settings.
    2. In the Client Certificates section, enter the following URL pattern to Automatically Select Client Certificate for These Sites:
      {"pattern": "https://[*.]","filter":{}}
    3. Click Save. The Google Admin console deploys the policy to all devices within a few minutes.
    On the GlobalProtect Portal Configuration dialog (NetworkGlobalProtectPortals<portal-config>), select Authentication to choose the Certificate Profile to authenticate users based on a client certificate or smart card.
    The Common Name (CN) and, if applicable, the Subject Alternative Name (SAN) fields of the certificate must exactly match the IP address or FQDN of the interface where you configure the portal or HTTPS connections to the portal will fail.
  5. Save the portal configuration.
    1. Click OK to save your configuration.
    2. Commit the changes.

Related Documentation