Enable SSL Between GlobalProtect LSVPN Components
All interaction between the GlobalProtect components occurs over an SSL/TLS connection. Therefore, you must generate and/or install the required certificates before configuring each component so that you can reference the appropriate certificate(s) and/or certificate profiles in the configurations for each component. The following sections describe the supported methods of certificate deployment, descriptions and best practice guidelines for the various GlobalProtect certificates, and provide instructions for generating and deploying the required certificates:
About Certificate Deployment
There are two basic approaches to deploying certificates for GlobalProtect LSVPN:
Enterprise Certificate Authority —If you already have your own enterprise certificate authority, you can use this internal CA to issue an intermediate CA certificate for the GlobalProtect portal to enable it to issue certificates to the GlobalProtect gateways and satellites. You can also configure the GlobalProtect portal to act as a Simple Certificate Enrollment Protocol (SCEP) client to issue client certificates to GlobalProtect satellites. Self-Signed Certificates —You can generate a self-signed root CA certificate on the firewall and use it to issue server certificates for the portal, gateway(s), and satellite(s). As a best practice, create a self-signed root CA certificate on the portal and use it to issue server certificates for the gateways and satellites. This way, the private key used for certificate signing stays on the portal.
Deploy Server Certificates to the GlobalProtect LSVPN Components
The GlobalProtect LSVPN components use SSL/TLS to mutually authenticate. Before deploying the LSVPN, you must assign an SSL/TLS service profile to each portal and gateway. The profile specifies the server certificate and allowed TLS versions for communication with satellites. You don’t need to create SSL/TLS service profiles for the satellites because the portal will issue a server certificate for each satellite during the first connection as part of the satellite registration process.
In addition, you must import the root certificate authority (CA) certificate used to issue the server certificates onto each firewall that you plan to host as a gateway or satellite. Finally, on each gateway and satellite participating in the LSVPN, you must configure a certificate profile that will enable them to establish an SSL/TLS connection using mutual authentication.
The following workflow shows the best practice steps for deploying SSL certificates to the GlobalProtect LSVPN components:
Deploy SSL Server Certificates to the GlobalProtect Components
On the firewall hosting the GlobalProtect portal, create the root CA certificate for signing the certificates of the GlobalProtect components. Create a Self-Signed Root CA Certificate: Select Device > Certificate Management > Certificates > Device Certificates and click Generate. Enter a Certificate Name, such as LSVPN_CA . Do not select a value in the Signed By field (this is what indicates that it is self-signed). Select the Certificate Authority check box and then click OK to generate the certificate.
Create SSL/TLS service profiles for the GlobalProtect portal and gateways. For the portal and each gateway, you must assign an SSL/TLS service profile that references a unique self-signed server certificate. The best practice is to issue all of the required certificates on the portal, so that the signing certificate (with the private key) doesn’t have to be exported. If the GlobalProtect portal and gateway are on the same firewall interface, you can use the same server certificate for both components. Use the root CA on the portal to Generate a Certificate for each gateway you will deploy: Select Device > Certificate Management > Certificates > Device Certificates and click Generate. Enter a Certificate Name. Enter the FQDN (recommended) or IP address of the interface where you plan to configure the gateway in the Common Name field. In the Signed By field, select the LSVPN_CA certificate you just created. In the Certificate Attributes section, click Add and define the attributes to uniquely identify the gateway. If you add a Host Name attribute (which populates the SAN field of the certificate), it must exactly match the value you defined for the Common Name. Generate the certificate. Configure an SSL/TLS Service Profile for the portal and each gateway: Select Device > Certificate Management > SSL/TLS Service Profile and click Add. Enter a Name to identify the profile and select the server Certificate you just created for the portal or gateway. Define the range of TLS versions ( Min Version to Max Version) allowed for communicating with satellites and click OK.
Deploy the self-signed server certificates to the gateways. Best Practices: Export the self-signed server certificates issued by the root CA from the portal and import them onto the gateways. Be sure to issue a unique server certificate for each gateway. The Common Name (CN) and, if applicable, the Subject Alternative Name (SAN) fields of the certificate must match the IP address or fully qualified domain name (FQDN) of the interface where you configure the gateway. On the portal, select Device > Certificate Management > Certificates > Device Certificates, select the gateway certificate you want to deploy, and click Export. Select Encrypted Private Key and Certificate (PKCS12) from the File Format drop-down. Enter (and re-enter) a Passphrase to encrypt the private key associated with the certificate and then click OK to download the PKCS12 file to your computer. On the gateway, select Device > Certificate Management > Certificates > Device Certificates and click Import. Enter a Certificate Name. Enter the path and name to the Certificate File you just downloaded from the portal, or Browse to find the file. Select Encrypted Private Key and Certificate (PKCS12) as the File Format. Enter the path and name to the PKCS12 file in the Key File field or Browse to find it. Enter and re-enter the Passphrase you used to encrypt the private key when you exported it from the portal and then click OK to import the certificate and key.
Import the root CA certificate used to issue server certificates for the LSVPN components. You must import the root CA certificate onto all gateways and satellites. For security reasons, make sure you export the certificate only, and not the associated private key. Download the root CA certificate from the portal. Select Device > Certificate Management > Certificates > Device Certificates. Select the root CA certificate used to issue certificates for the LSVPN components and click Export. Select Base64 Encoded Certificate (PEM) from the File Format drop-down and click OK to download the certificate. (Do not export the private key.) On the firewalls hosting the gateways and satellites, import the root CA certificate. Select Device > Certificate Management > Certificates > Device Certificates and click Import. Enter a Certificate Name that identifies the certificate as your client CA certificate. Browse to the Certificate File you downloaded from the CA. Select Base64 Encoded Certificate (PEM) as the File Format and then click OK. Select the certificate you just imported on the Device Certificates tab to open it. Select Trusted Root CA and then click OK. Commit the changes.
Create a certificate profile. The GlobalProtect LSVPN portal and each gateway require a certificate profile that specifies which certificate to use to authenticate the satellites. Select Device > Certificate Management > Certificate Profile and click Add and enter a profile Name. Make sure Username Field is set to None. In the CA Certificates field, click Add, select the Trusted Root CA certificate you imported in the previous step. ( Optional, but recommended ) Enable use of CRL and/or OCSP to enable certificate status verification. Click OK to save the profile.
Save the configuration. Click Commit.
Deploy Client Certificates to the GlobalProtect Satellites Using SCEP
As an alternative method for deploying client certificates to satellites, you can configure your GlobalProtect portal to act as a Simple Certificate Enrollment Protocol (SCEP) client to a SCEP server in your enterprise PKI. SCEP operation is dynamic in that the enterprise PKI generates a certificate when the portal requests it and sends the certificate to the portal.
When the satellite device requests a connection to the portal or gateway, it also includes its serial number with the connection request. The portal submits a CSR to the SCEP server using the settings in the SCEP profile and automatically includes the serial number of the device in the subject of the client certificate. After receiving the client certificate from the enterprise PKI, the portal transparently deploys the client certificate to the satellite device. The satellite device then presents the client certificate to the portal or gateway for authentication.
Deploy Server Certificates to the GlobalProtect Components Using SCEP
Create a SCEP profile. Select Device > Certificate Management > SCEP and then Add a new profile. Enter a Name to identify the SCEP profile. If this profile is for a firewall with multiple virtual systems capability, select a virtual system or Shared as the Location where the profile is available.
( Optional ) To make the SCEP-based certificate generation more secure, configure a SCEP challenge-response mechanism between the PKI and portal for each certificate request. After you configure this mechanism, its operation is invisible, and no further input from you is necessary. To comply with the U.S. Federal Information Processing Standard (FIPS), use a Dynamic SCEP challenge and specify a Server URL that uses HTTPS (see Step 7). Select one of the following options: None —( Default ) The SCEP server does not challenge the portal before it issues a certificate. Fixed —Obtain the enrollment challenge password from the SCEP server (for example, http://10.200.101.1/CertSrv/mscep_admin/ ) in the PKI infrastructure and then copy or enter the password into the Password field. Dynamic —Enter the SCEP Server URL where the portal-client submits these credentials (for example, http://10.200.101.1/CertSrv/mscep_admin/ ), and a username and OTP of your choice. The username and password can be the credentials of the PKI administrator.
Specify the settings for the connection between the SCEP server and the portal to enable the portal to request and receive client certificates. To identify the satellite, the portal automatically includes the device serial number in the CSR request to the SCEP server. Because the SCEP profile requires a value in the Subject field, you can leave the default $USERNAME token even though the value is not used in client certificates for LSVPN. Configure the Server URL that the portal uses to reach the SCEP server in the PKI (for example, http://10.200.101.1/certsrv/mscep/ ). Enter a string (up to 255 characters in length) in the CA-IDENT Name field to identify the SCEP server. Select the Subject Alternative Name Type: RFC 822 Name —Enter the email name in a certificate’s subject or Subject Alternative Name extension. DNS Name —Enter the DNS name used to evaluate certificates. Uniform Resource Identifier —Enter the name of the resource from which the client will obtain the certificate. None —Do not specify attributes for the certificate.
( Optional ) Configure cryptographic settings for the certificate. Select the key length ( Number of Bits) for the certificate. If the firewall is in FIPS-CC mode and the key generation algorithm is RSA. The RSA keys must be 2048 bits or larger. Select the Digest for CSR which indicates the digest algorithm for the certificate signing request (CSR): SHA1, SHA256, SHA384, SHA512.
( Optional ) Configure the permitted uses of the certificate, either for signing or encryption. To use this certificate for signing, select the Use as digital signature check box. This enables the endpoint use the private key in the certificate to validate a digital signature. To use this certificate for encryption, select the Use for key encipherment check box. This enables the client use the private key in the certificate to encrypt data exchanged over the HTTPS connection established with the certificates issued by the SCEP server.
( Optional ) To ensure that the portal is connecting to the correct SCEP server, enter the CA Certificate Fingerprint. Obtain this fingerprint from the SCEP server interface in the Thumbprint field. Enter the URL for the SCEP server’s administrative UI (for example, http://<hostname or IP>/CertSrv/mscep_admin/ ). Copy the thumbprint and enter it in the CA Certificate Fingerprint field.
Enable mutual SSL authentication between the SCEP server and the GlobalProtect portal. This is required to comply with the U.S. Federal Information Processing Standard (FIPS). FIPS-CC operation is indicated on the firewall login page and in its status bar. Select the SCEP server’s root CA Certificate. Optionally, you can enable mutual SSL authentication between the SCEP server and the GlobalProtect portal by selecting a Client Certificate.
Save and commit the configuration. Click OK to save the settings and close the SCEP configuration. Commit the configuration. The portal attempts to request a CA certificate using the settings in the SCEP profile and saves it to the firewall hosting the portal. If successful, the CA certificate is shown in Device > Certificate Management > Certificates.
( Optional ) If after saving the SCEP profile, the portal fails to obtain the certificate, you can manually generate a certificate signing request (CSR) from the portal. Select Device > Certificate Management > Certificates > Device Certificates and then click Generate. Enter a Certificate Name. This name cannot contain spaces. Select the SCEP Profile to use to submit a CSR to your enterprise PKI. Click OK to submit the request and generate the certificate.

Related Documentation