Enable Two-Factor Authentication Using Certificate and Authentication Profiles

The following workflow describes how to configure GlobalProtect client authentication requiring the user to authenticate both to a certificate profile and an authentication profile. The user must successfully authenticate using both methods in order to connect to the portal/gateway. For more details on this configuration, see Remote Access VPN with Two-Factor Authentication.
  1. Create an authentication server profile.
    The authentication server profile determines how the firewall connects to an external authentication service and retrieves the authentication credentials for your users.
    If you are using LDAP to connect to Active Directory (AD), you must create a separate LDAP server profile for every AD domain.
    1. Select
      Device
      Server Profiles
      and a profile type (
      LDAP
      ,
      Kerberos
      ,
      RADIUS
      , or
      TACACS⁠+
      ).
    2. Add
      a new server profile.
    3. Enter a
      Profile
      Name
      for the profile, such as GP-User-Auth.
    4. (
      LDAP only
      ) Select the
      Type
      of LDAP server (
      active-directory
      ,
      e-directory
      ,
      sun
      , or
      other
      ).
    5. Click
      Add
      in the Servers list section and then enter the required information for connections to the authentication service, including the server
      Name
      , IP address or FQDN of the
      Server
      , and
      Port
      .
    6. (
      RADIUS, TACACS+, and LDAP only
      ) Specify settings to enable the firewall to authenticate to the authentication service as follows:
      • RADIUS and TACACS+—Enter the shared
        Secret
        when adding the server entry.
      • LDAP—Enter the
        Bind DN
        and
        Password
        .
    7. (
      LDAP only
      ) If you want the endpoint to use SSL or TLS for a more secure connection with the directory server, select the
      Require SSL/TLS secured connection
      check box (selected by default). The protocol that the device uses depends on the server
      Port
      in the
      Server list
      :
      • 389 (default)—TLS (specifically, the device uses the StartTLS operation to upgrade the initial plaintext connection to TLS).
      • 636—SSL.
      • Any other port—The device first attempts to use TLS. If the directory server does not support TLS, the device uses SSL.
    8. (
      LDAP only
      ) For additional security, select the
      Verify Server Certificate for SSL sessions
      check box so that the endpoint verifies the certificate that the directory server presents for SSL/TLS connections. To enable verification, you also must select the
      Require SSL/TLS secured connection
      check box. For verification to succeed, one of the following conditions must be true:
      • The certificate is in the list of device certificates:
        Device
        Certificate Management
        Certificates
        Device Certificates
        . Import the certificate into the endpoint if necessary.
      • The certificate signer is in the list of trusted certificate authorities:
        Device
        Certificate Management
        Certificates
        Default Trusted Certificate Authorities
        .
    9. Click
      OK
      to save the server profile.
  2. Create an authentication profile that identifies the service for authenticating users. (You later have the option of assigning the profile on the portal and on gateways.)
    1. Select
      Device
      Authentication Profile
      and
      Add
      a new profile.
    2. Enter a
      Name
      for the profile.
    3. Select the
      Location
      .
    4. Select the
      Type
      of
      Authentication
      (
      LDAP
      ,
      Kerberos
      ,
      RADIUS
      , or
      TACACS+
      ).
    5. Select the
      Server Profile
      you created in 1.
    6. (
      LDAP only
      ) Enter
      sAMAccountName
      as the
      Login Attribute
      .
    7. Click
      OK
      to save the authentication profile.
  3. Create a client certificate profile that the portal uses to authenticate the client certificates that come from user devices.
    When you configure two-factor authentication to use client certificates, the external authentication service uses the username value to authenticate the user, if specified, in the client certificate. This ensures that the user who is logging is in is actually the user to whom the certificate was issued.
    1. Select
      Device
      Certificates
      Certificate Management
      Certificate Profile
      and click
      Add
      and enter a profile
      Name
      .
    2. Select a value for the
      Username Field
      :
      • If you intend for the client certificate to authenticate individual users, select the certificate field that identifies the user.
      • If you are deploying the client certificate from the portal, leave this field set to
        None
        .
      • If you are setting up a certificate profile for use with a pre-logon connect method, leave the field set to
        None
        .
    3. In the
      CA Certificates
      area, click
      Add
      and then:
      1. Select the
        CA certificate
        , either a trusted root CA certificate or the CA certificate from a SCEP server. (If necessary, import the certificate).
      2. (
        Optional
        ) Enter the
        Default OCSP URL
        .
      3. (
        Optional
        ) Select a certificate for
        OCSP Verify CA
        .
    4. (
      Optional
      ) Select options that specify when to block the user’s requested session:
      1. Status of certificate is unknown.
      2. GlobalProtect component does not retrieve certificate status within the number of seconds in
        Certificate Status Timeout
        .
      3. Serial number attribute in the subject of a client certificate does not match the host ID that the GlobalProtect agent reports for the client endpoint.
    5. Click
      OK
      .
  4. To transparently deploy client certificates, configure your portal to distribute a shared client certificate to your endpoints or configure the portal to use SCEP to request and deploy unique client certificates for each user.
    1. Use your enterprise PKI or a public CA to issue a client certificate to each GlobalProtect user.
    2. For the pre-logon connect methods, install certificates in the personal certificate store on the client systems.
  5. Save the GlobalProtect configuration.
    Click
    Commit
    .

Related Documentation