How to Use a Wildcard SSL Cert with Subject Alternative Names for GlobalProtect Portal/Gateway.

Printer Friendly Page


This document describes how to use a wildcard (multi-domain) certificate with one common name and Subject Alternative Names (SAN) for other protected domains. The DNS names for GlobalProtect Portal and each GlobalProtect Gateway are assumed to be listed as SANs.



  1. Create a CA root certificate.
  2. Create a new certificate and have it signed by the above generated CA root certificate. This will be the wildcard certificate that will be used for the GlobalProtect Portal and Gateway. For example:
       Name: GP-Cert
       Common Name: *
       Subject Alternative Name:  DNS,  DNS
  3. Associate the hostnames for the GlobalProtect Portal and Gateway IP addresses. For example:
      GlobalProtect Portal IP address:
      GlobalProtect Gateway IP address:
    Note: If GlobalProtect Portal and Gateway share the same IP address (i.e. Palo Alto Networks firewall interface is configured as both portal and gateway), a single hostname can be used for the shared IP address. For this example, the portal and gateway hostname would be:
  4. Import the certificates under the certificate cache of the GlobalProtect Portal firewall and each GlobalProtect Gateway firewalls (in a multi-gateway setup)
    • In PAN-OS 4.0 and 4.1, the certificates are located at Device > Certificates
    • In PAN-OS 5.0, the certificates are located at Device > Certificate Management > Certificates
  5. Single firewall deployment - Follow the portal configuration steps in GlobalProtect Configuration Tech Note, along with the steps below:
    • Use the GP-CERT (from step 2) as the server certificate under the portal configuration
    • Use the CA root certificate (from step 1) under the "trusted root CA" section of the "Client configuration"
    • Specify the external gateway address. For this example, the gateway is ""

For multi-gateway deployment, follow the gateway configuration steps in GlobalProtect Configuration Tech Note, and use the GP-CERT certificate (from step 2) under the server certificate section.


Just FYI, the DNS Names would be added under the Certificate Attributes section of the certificate as "Host Name".

See the example below.


What if just importing it with passphrase? 

This doesnt help if you are using an official public wildcard certificate which does not list any SANs. GlobalProtect is too finicky about certificates.