Palo Alto Networks Knowledgebase: How to Install a Chained Certificate Signed by a Public CA

How to Install a Chained Certificate Signed by a Public CA

16796
Created On 02/08/19 00:04 AM - Last Updated 02/08/19 00:04 AM
Resolution

Overview

When configuring a Palo Alto Networks Next Generation Firewall, a certificate signed by a trusted public Certificate Authority (CA) may be desired on:

 

  • Captive Portal ("CP") pages
  • Response Pages
  • GlobalProtect ("GP") Portal

Many public CAs use chained certificates, that is, certificates not signed by the Root CA itself, but one or more Intermediate CAs. These are usually owned and operated by the same CA but gives that CA flexibility and ease of revocation if a problem arises.

 

Steps

1. Requesting the certificate

Depending on which PAN-OS version is installed on the firewall, a private key and CSR may need to be generated on a third-party program such as OpenSSL.

If using PAN-OS 5.0, refer to How to Generate a CSR(Certificate Signing Request) and Import the Signed Certificate

 

2. Creating the combination certificate

When a certificate is not signed by the Root CA, the intermediate CAs should be sent to clients in case those clients do not have the intermediate CAs in their trusted key store already. To do that, a combination certificate that consists of the signed certificate (CP, GP, and so on), followed by the intermediate CAs. The image below shows two, but the same process is valid for only one intermediate CA or several.

Cert_Chain_markup.png

 

To get each of these certificates:

  • Open the "Server Cert" file sent by the CA.
  • In Windows, the certificate dialog box has three tabs: General, Details, and Certification Path.
  • Click the Certification Path and click the certificate one step above the bottom.
  • Open that certificate and click the Details tab, then Copy To File.
  • Save the file as a Base-64 encoded X.509 (.CER) formatted certificate.
  • Do the same for all certificates in the chain except the top (Root).
  • Open each certificate .CER file in a plain-text editor (such as Notepad).
  • Paste each certificate end-to-end, with the Server Cert on top and each signer below that.
  • Save the file as a .TXT or .CER file
    Note: The name of the file cannot contain spaces, as this may cause the import to fail.

3. Importing the Certificate

Take the combined certificate and import it on the firewall.

 

Workaround

In the event that you can not generate a new CSR , but still need to export a certificate, please try these Steps:

  1. Export the current Certificate on the Firewall , PEM format and with Private key exported.
  2. Open the cert in a Text editor.
  3. Separate the public key from the private key in two separate text files (being careful not to add any spaces).
  4. Save the private key text file and keep it aside.
  5. Edit the file where the public key is and have the public key at the top and add the intermediate CA below it as in the url shared, and save the file.
  6. Delete the certificate already on the firewall.
  7. Import the private key with the edited certificate.

 

owner: gwesson



Attachments
Actions
  • Print
  • Copy Link

    https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClkoCAC&refURL=http%3A%2F%2Fknowledgebase.paloaltonetworks.com%2FKCSArticleDetail

Attachments
Choose Language