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 Two-Factor Authentication.
- Issue client certificates to GlobalProtect clients and endpoints.This enables the GlobalProtect portal and gateways to validate that the device belongs to your organization.
- Selectand then clickDeviceCertificate ManagementCertificatesDevice CertificatesGenerate.
- Enter aCertificate Name. The certificate name cannot contain any spaces.
- Configure cryptographic settings for the certificate including the encryptionAlgorithm, key length (Number of Bits),Digestalgorithm (use sha1, sha256, or sha384; sha512 is not supported with client certificates), andExpiration(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.
- In the Certificate Attributes section,Addand define the attributes that uniquely identify the GlobalProtect clients as belonging to your organization. Keep in mind that if you add aHost Nameattribute (which populates the SAN field of the certificate), it must be the same as the value you defined for theCommon Name.
- In theSigned Byfield, select your root CA.
- Select anOCSP Responderto verify the revocation status of certificates.
- (Optional) In the Certificate Attributes section, clickAddand define the attributes to identify the GlobalProtect clients as belonging to your organization if required as part of your security requirements.
- ClickOKto generate the certificate.
- 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:
- From the command prompt, entermmcto launch the console.
- Select.FileAdd/Remove Snap-in
- SelectCertificates, clickAddand 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.
- ExpandCertificatesand selectPersonaland then in the Actions column selectand follow the steps in the Certificate Import Wizard to import the PKCS file you got from the CA.PersonalMore ActionsAll TasksImport
- Browse to the .p12 certificate file to import (selectPersonal Information Exchangeas the file type to browse for) and enter thePasswordthat you used to encrypt the private key. SelectPersonalas theCertificate store.
- Verify that the certificate has been added to the personal certificate store.Navigate to the personal certificate store:
- 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.
- Download the root CA certificate used to issue the client certificates (Base64 format).
- Import the root CA certificate from the CA that generated the client certificates onto the firewall:
- Selectand clickDeviceCertificate ManagementCertificatesDevice CertificatesImport.
- Use theLocalcertificate type (the default).
- Enter aCertificate Namethat identifies the certificate as your client CA certificate.
- Browseto theCertificate Fileyou downloaded from the CA.
- SelectBase64 Encoded Certificate (PEM)as theFile Formatand then clickOK.
- Select the certificate you just imported on theDevice Certificatestab to open it.
- SelectTrusted Root CAand then clickOK.
- Create a client certificate profile.
- Select, clickDeviceCertificatesCertificate ManagementCertificate ProfileAdd, and enter a profileName.
- Select a value for theUsername Fieldto 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 theUsername 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 ofNone, 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.
- In theCA Certificatesfield, clickAdd, select the Trusted Root CA certificate you imported in 4 and then clickOK.
- Save the configuration.ClickCommit.
Recommended For You
Recommended videos not found.