Palo Alto Panorama/Firewall Orchestrator for Add, Remove and Inventory.
This repository contains a Universal Orchestrator Extension which is a plugin to the Keyfactor Universal Orchestrator. Within the Keyfactor Platform, Orchestrators are used to manage “certificate stores” — collections of certificates and roots of trust that are found within and used by various applications.
The Universal Orchestrator is part of the Keyfactor software distribution and is available via the Keyfactor customer portal. For general instructions on installing Extensions, see the “Keyfactor Command Orchestrator Installation and Configuration Guide” section of the Keyfactor documentation. For configuration details of this specific Extension see below in this readme.
The Universal Orchestrator is the successor to the Windows Orchestrator. This Orchestrator Extension plugin only works with the Universal Orchestrator and does not work with the Windows Orchestrator.
Palo Alto Orchestrator is supported by Keyfactor for Keyfactor customers. If you have a support issue, please open a support ticket via the Keyfactor Support Portal at https://support.keyfactor.com
To report a problem or suggest a new feature, use the Issues tab. If you want to contribute actual bug fixes or proposed enhancements, use the Pull requests tab.
The minimum version of the Keyfactor Universal Orchestrator Framework needed to run this version of the extension is 10.1
The Keyfactor Universal Orchestrator may be installed on either Windows or Linux based platforms. The certificate operations supported by a capability may vary based what platform the capability is installed on. The table below indicates what capabilities are supported based on which platform the encompassing Universal Orchestrator is running.
| Operation | Win | Linux |
|---|---|---|
| Supports Management Add | ✓ | |
| Supports Management Remove | ✓ | |
| Supports Create Store | ||
| Supports Discovery | ||
| Supports Renrollment | ✓ | |
| Supports Inventory | ✓ |
This orchestrator extension has the ability to connect to a variety of supported PAM providers to allow for the retrieval of various client hosted secrets right from the orchestrator server itself. This eliminates the need to set up the PAM integration on Keyfactor Command which may be in an environment that the client does not want to have access to their PAM provider.
The secrets that this orchestrator extension supports for use with a PAM Provider are:
| Name | Description |
|---|---|
| ServerPassword | Key obtained from Palo Alto API to authenticate the server hosting the store |
It is not necessary to use a PAM Provider for all of the secrets available above. If a PAM Provider should not be used, simply enter in the actual value to be used, as normal.
If a PAM Provider will be used for one of the fields above, start by referencing the Keyfactor Integration Catalog. The GitHub repo for the PAM Provider to be used contains important information such as the format of the json needed. What follows is an example but does not reflect the json values for all PAM Providers as they have different "instance" and "initialization" parameter names and values.
General PAM Provider Configuration
To use a PAM Provider to resolve a field, in this example the Server Password will be resolved by the Hashicorp-Vault provider, first install the PAM Provider extension from the Keyfactor Integration Catalog on the Universal Orchestrator.
Next, complete configuration of the PAM Provider on the UO by editing the manifest.json of the PAM Provider (e.g. located at extensions/Hashicorp-Vault/manifest.json). The "initialization" parameters need to be entered here:
"Keyfactor:PAMProviders:Hashicorp-Vault:InitializationInfo": {
"Host": "http://127.0.0.1:8200",
"Path": "v1/secret/data",
"Token": "xxxxxx"
}After these values are entered, the Orchestrator needs to be restarted to pick up the configuration. Now the PAM Provider can be used on other Orchestrator Extensions.
With the PAM Provider configured as an extenion on the UO, a json object can be passed instead of an actual value to resolve the field with a PAM Provider. Consult the Keyfactor Integration Catalog for the specific format of the json object.
To have the Server Password field resolved by the Hashicorp-Vault provider, the corresponding json object from the Hashicorp-Vault extension needs to be copied and filed in with the correct information:
{"Secret":"my-kv-secret","Key":"myServerPassword"}This text would be entered in as the value for the Server Password, instead of entering in the actual password. The Orchestrator will attempt to use the PAM Provider to retrieve the Server Password. If PAM should not be used, just directly enter in the value for the field.
Palo Alto Orchestrator Device Configuration
Overview
The Palo Alto Orchestrator remotely manages certificates on either the Palo Alto PA-VM Firewall Device or the Panorama. If using Panorama, it will push changes to all the devices from Panorama.
This agent implements three job types – Inventory, Management Add, and Management Remove. Below are the steps necessary to configure this Orchestrator. It supports adding certificates with or without private keys.
NOTE: Palo Alto does not support incremental certificate inventory. If you have large numbers of certificates in your environment it is recommended to limit the frequency of inventory jobs to 30 minutes or more.
1. Create the New Certificate Store Type for either the PA-VM Firewall Device or Panorama
In Keyfactor Command create a new Certificate Store Type similar to the one below:
| SETTING TAB | CONFIG ELEMENT | DESCRIPTION |
|---|---|---|
| Basic | Name | Descriptive name for the Store Type. PaloAlto can be used. |
| Basic | Short Name | The short name that identifies the registered functionality of the orchestrator. Must be PaloAlto |
| Basic | Custom Capability | You can leave this unchecked and use the default. |
| Basic | Job Types | Inventory, Add, and Remove are the supported job types. |
| Basic | Needs Server | Must be checked |
| Basic | Blueprint Allowed | Unchecked |
| Basic | Requires Store Password | Determines if a store password is required when configuring an individual store. This must be unchecked. |
| Basic | Supports Entry Password | Determined if an individual entry within a store can have a password. This must be unchecked. |
| Advanced | Store Path Type | Determines how the user will enter the store path when setting up the cert store. Freeform |
| Advanced | Supports Custom Alias | Determines if an individual entry within a store can have a custom Alias. This must be Required |
| Advanced | Private Key Handling | Determines how the orchestrator deals with private keys. Optional |
| Advanced | PFX Password Style | Determines password style for the PFX Password. Default |
| NAME | DISPLAY NAME | TYPE | DEFAULT VALUE | DEPENDS ON | REQUIRED | DESCRIPTION |
|---|---|---|---|---|---|---|
| ServerUsername | Server Username | Secret | Unchecked | Yes | Palo Alto Api User Name | |
| ServerPassword | Server Password | Secret | Unchecked | Yes | Palo Alto Api Password | |
| ServerUseSsl | Use SSL | Bool | True | Unchecked | Yes | Requires SSL Connection |
| DeviceGroup | Device Group | String | Unchecked | No | Device Group on Panorama that changes will be pushed to. |
| NAME | DISPLAY NAME | TYPE | DEFAULT VALUE | DEPENDS ON | REQUIRED WHEN | DESCRIPTION |
|---|---|---|---|---|---|---|
| Trusted Root | Trusted Root | Bool | False | Unchecked | Adding an Entry | Will set the certificate as Trusted Root in Panorama or on the Firewall |
| TlsMinVersion | TLS Min Version | Multiple Choice | Unchecked | No | Min TLS Version for the Binding (,tls1-0,tls1-1,tls1-2) note first multiple choice item is empty | |
| TlsMaxVersion | TLS Max Version | Multiple Choice | Unchecked | No | Max TLS Version for the Binding (,tls1-0,tls1-1,tls1-2,max) note first multiple choice item is empty | |
| TlsProfileName | TLS Profile Name | String | Unchecked | No | Name of the binding to deploy certificate to | |
| ServerUseSsl | Use SSL | Bool | True | Unchecked | Yes | Requires SSL Connection |
2. Register the PaloAlto Orchestrator with Keyfactor See Keyfactor InstallingKeyfactorOrchestrators.pdf Documentation. Get from your Keyfactor contact/representative.
3. Create a Palo Alto Certificate Store within Keyfactor Command
In Keyfactor Command create a new Certificate Store similar to the one below
| CONFIG ELEMENT | DESCRIPTION |
|---|---|
| Category | The type of certificate store to be configured. Select category based on the display name configured above "PaloAlto". |
| Container | This is a logical grouping of like stores. This configuration is optional and does not impact the functionality of the store. |
| Client Machine | The hostname of the Panorama or Firewall. Sample is "keyfactorpa.eastus2.cloudapp.azure.com". |
| Store Path | If Panorama it is the name of the Template in Panorama if Firewall then "/" |
| Orchestrator | This is the orchestrator server registered with the appropriate capabilities to manage this certificate store type. |
| Inventory Schedule | The interval that the system will use to report on what certificates are currently in the store. |
| Use SSL | This should be checked. |
| User | ApiUser Setup for either Panorama or the Firewall Device |
| Password | Api Password Setup for the user above |
| Tab | Security Items |
|---|---|
| Xml Api | Report,Log,Configuration,Operational Requests,Commit,Export,Import |
| Rest Api | Objects/Devices,Panorama/Scheduled Config Push,Panorama/Templates,Panorama/Template Stacks,Panorama/Device Groups,System/Configuration,Plugins/Plugins |
| Case Number | Store Path | Screenshot/Description |
|---|---|---|
| TC1 | / |  |
| TC2 | / |  |
| TC3 | / |  |
| TC4 | / |  |
| TC5 | / |  |
| TC6 | / |  |
| TC7 | / |  |
| TC8 | / |  |
| TC9 | / |  |
| TC10 | / |  |
| TC11 | / |  |
| TC12 | CertificatesTemplate |   |
| TC13 | CertificatesTemplate |   |
| TC14 | CertificatesTemplate |   |
| TC15 | CertificatesTemplate |   |
| TC16 | CertificatesTemplate |   |
| TC17 | CertificatesTemplate |     |
| TC18 | CertificatesTemplate |     |
| TC19 | CertificatesTemplate |  |
| TC20 | CertificatesTemplate |  |
| TC21 | CertificatesTemplate |   |
| TC22 | CertificatesTemplate |  |
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent