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 devices. For example, you can configure Android users to use RADIUS authentication and Windows users to use LDAP authentication. You can also customize the client authentication for users who access the portal from a web browser (to download the GlobalProtect agent) or for third-party IPSec VPN (X-Auth) access to GlobalProtect gateways.
    1. Select
      Network
      GlobalProtect
      Portals
      .
    2. Select the portal configuration to which you are adding the client configuration and then select the
      Authentication
      tab.
  1. Specify how the portal authenticates the users.
    You can configure the GlobalProtect portal to authenticate users using 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.
    In the Client Authentication area,
    Add
    a new configuration with the following settings:
    • Enter a
      Name
      to identify the client authentication configuration.
    • Specify the endpoints to which to deploy this configuration. By default, the configuration applies to all endpoints. Otherwise, you can apply the configuration to endpoints running a specific
      OS
      (
      Android
      ,
      Chrome
      ,
      iOS
      ,
      Mac
      ,
      Windows
      , or
      WindowsUWP
      ) or to endpoints that access the portal from a web
      Browser
      with the intent of downloading the GlobalProtect agent or to create a new client authentication specifically for GlobalProtect Clientless VPN.
    • Select or add an
      Authentication Profile
      for authenticating an endpoint that tries to access the gateway.
    • Enter an
      Authentication Message
      to help end users understand which credentials to use when logging in. The message can be up to 100 characters in length (default is
      Enterlogin credentials
      ).
  2. 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. 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 agent or 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
      .
  3. (
    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 client 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 management
      Chrome management
      User 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.
    Select the corresponding
    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.
  4. Save the portal configuration.
    1. Click
      OK
      to save the settings and close the GlobalProtect Portal Configuration dialog.
    2. Commit
      the changes.

Related Documentation