Deploy Machine Certificates for Authentication

To confirm that the endpoint belongs to your organization, use your own public-key infrastructure (PKI) to issue and distribute machine certificates to each endpoint (recommended) or generate a self-signed machine certificate for export. With the pre-logon connect methods, a machine certificate is required and must be installed on the endpoint before GlobalProtect components will grant access.
To confirm that the endpoint belongs to your organization, you must also configure an authentication profile to authenticate the user. See Set Up Two-Factor Authentication .
Use the following workflow to create the client certificate and manually deploy it to an endpoint. For more information, see About GlobalProtect User Authentication . For an example configuration, see Remote Access VPN (Certificate Profile) .
  1. Issue client certificates to GlobalProtect clients and endpoints. This enables the GlobalProtect portal and gateways to validate that the device belongs to your organization.
    1. Create the root CA certificate for issuing self-signed certificates for the GlobalProtect components.
    2. Select DeviceCertificate ManagementCertificatesDevice Certificates and then click Generate.
    3. Enter a Certificate Name. The certificate name cannot contain any spaces.
    4. Configure cryptographic settings for the certificate including the encryption Algorithm, key length (Number of Bits), Digest algorithm (use sha1, sha256, or sha384; sha512 is not supported with client certificates), and Expiration (in days) for the certificate.
      If the firewall is in FIPS-CC mode and the key generation algorithm is RSA, the RSA keys must be 2,048 bits or 3072 bits.
    5. In the Certificate Attributes section, Add and define the attributes that uniquely identify the GlobalProtect clients as belonging to your organization. Keep in mind that if you add a Host Name attribute (which populates the SAN field of the certificate), it must be the same as the value you defined for the Common Name.
    6. In the Signed By field, select your root CA.
    7. Select an OCSP Responder to verify the revocation status of certificates.
    8. (Optional) In the Certificate Attributes section, click Add and define the attributes to identify the GlobalProtect clients as belonging to your organization if required as part of your security requirements.
    9. Click OK to generate the certificate.
  2. Install certificates in the personal certificate store on the endpoints.
    If you are using unique user certificates or machine certificates, you must install each certificate in the personal certificate store on the endpoint prior to the first portal or gateway connection. Install machine certificates to the Local Computer certificate store on Windows and in the System Keychain on Mac OS. Install user certificates to the Current User certificate store on Windows and in the Keychain on Mac OS.
    For example, to install a certificate on a Windows system using the Microsoft Management Console:
    1. From the command prompt, enter mmc to launch the console.
    2. Select FileAdd/Remove Snap-in.
    3. Select Certificates, click Add and then select one of the following, depending on what type of certificate you are importing:
      • Computer account—Select this option if you are importing a machine certificate.
      • My user account—Select this option if you are importing a user certificate.
      machine_cert1.png
    4. Expand Certificates and select Personal and then in the Actions column select PersonalMore ActionsAll TasksImport and follow the steps in the Certificate Import Wizard to import the PKCS file you got from the CA.
      machine_cert2.png
    5. Browse to the .p12 certificate file to import (select Personal Information Exchange as the file type to browse for) and enter the Password that you used to encrypt the private key. Select Personal as the Certificate store.
  3. Verify that the certificate has been added to the personal certificate store.
    Navigate to the personal certificate store:
    client_cert3.png
  4. Import the root CA certificate used to issue the client certificates onto the firewall.
    This step is required only if an external CA issued the client certificates, such as a public CA or an enterprise PKI CA. If you are using self-signed certificates, the root CA is already trusted by the portal and gateways.
    1. Download the root CA certificate used to issue the client certificates (Base64 format).
    2. Import the root CA certificate from the CA that generated the client certificates onto the firewall:
      1. Select DeviceCertificate ManagementCertificatesDevice Certificates and click Import.
      2. Use the Local certificate type (the default).
      3. Enter a Certificate Name that identifies the certificate as your client CA certificate.
      4. Browse to the Certificate File you downloaded from the CA.
      5. Select Base64 Encoded Certificate (PEM) as the File Format and then click OK.
      6. Select the certificate you just imported on the Device Certificates tab to open it.
      7. Select Trusted Root CA and then click OK.
  5. Create a client certificate profile.
    1. Select DeviceCertificatesCertificate ManagementCertificate Profile, click Add, and enter a profile Name.
    2. Select a value for the Username Field to specify which field in the certificate will contain the user’s identity information.
      If you plan to configure the portal or gateways to authenticate users with certificates only, you must specify the Username Field. This enables GlobalProtect to associate a username with the certificate.
      If you plan to set up the portal or gateway for two-factor authentication, you can leave the default value of None, or, to add an additional layer of security, specify a username. If you specify a username, your external authentication service verifies that the username in the client certificate matches the username requesting authentication. This ensures that the user is the one to which the certificate was issued.
      Users cannot change the username that is included in the certificate.
    3. In the CA Certificates field, click Add, select the Trusted Root CA certificate you imported in 4 and then click OK.
  6. Save the configuration.
    Click Commit.

Related Documentation