GetHostCertificate(
+ string domain,
+ string cloudflareHost = "www.cloudflare.com");
+}
diff --git a/Cloudflare/manifest.json b/Cloudflare/manifest.json
index 81d7653..f3cd757 100644
--- a/Cloudflare/manifest.json
+++ b/Cloudflare/manifest.json
@@ -1,13 +1,9 @@
{
"extensions": {
"Keyfactor.Orchestrators.Extensions.IOrchestratorJobExtension": {
- "CertStores.IISBindings.Inventory": {
- "assemblypath": "IISWithBindings.dll",
- "TypeFullName": "Keyfactor.Extensions.Orchestrator.IISWithBinding.Jobs.Inventory"
- },
- "CertStores.IISBindings.Management": {
- "assemblypath": "IISWithBindings.dll",
- "TypeFullName": "Keyfactor.Extensions.Orchestrator.IISWithBinding.Jobs.Management"
+ "CertStores.CloudflareEdge.Inventory": {
+ "assemblypath": "Cloudflare.dll",
+ "TypeFullName": "Keyfactor.Extensions.Orchestrator.CloudflareEdge.Jobs.Inventory"
}
}
}
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..f5137bc
--- /dev/null
+++ b/README.md
@@ -0,0 +1,295 @@
+
+ Cloudflare Edge Universal Orchestrator Extension
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Support
+
+ ·
+
+ Installation
+
+ ·
+
+ License
+
+ ·
+
+ Related Integrations
+
+
+
+## Overview
+
+The Cloudflare Edge Orchestrator Extension is an integration that can inventory [Cloudflare Edge certificates](https://developers.cloudflare.com/ssl/concepts/#edge-certificate).
+
+
+
+## Compatibility
+
+This integration is compatible with Keyfactor Universal Orchestrator version 11.0 and later.
+
+## Support
+The Cloudflare Edge Universal Orchestrator extension is supported by Keyfactor. If you require support for any issues or have feature request, please open a support ticket by either contacting your Keyfactor representative or via the Keyfactor Support Portal at https://support.keyfactor.com.
+
+> If you want to contribute bug fixes or additional enhancements, use the **[Pull requests](../../pulls)** tab.
+
+## Requirements & Prerequisites
+
+Before installing the Cloudflare Edge Universal Orchestrator extension, we recommend that you install [kfutil](https://github.com/Keyfactor/kfutil). Kfutil is a command-line tool that simplifies the process of creating store types, installing extensions, and instantiating certificate stores in Keyfactor Command.
+
+
+To inventory certificates, the Universal Orchestrator instance **must** be able to reach the server hosting the certificate over the network.
+Cloudflare's API does not provide the certificate contents, so the extension fetches the certificate directly from the server using a TLS handshake (via OpenSSL).
+
+### Authentication and Authorization
+
+When configuring the certificate store, the server password will contain the API token used to access the Cloudflare API. This can be either an **Account API Token** or a **User API Token**. See the [guide on how to create an API token](https://developers.cloudflare.com/fundamentals/api/get-started/create-token/).
+
+The API token must have the following permissions:
+
+|Permission|Required|Documentation|
+|--|--|--|
+|Account:SSL|Yes|[List Certificate Packs](https://developers.cloudflare.com/api/resources/ssl/subresources/certificate_packs/methods/list/)|
+|Certificates:Read|Yes|[List Certificate Packs](https://developers.cloudflare.com/api/resources/ssl/subresources/certificate_packs/methods/list/)|
+
+
+## CloudflareEdge Certificate Store Type
+
+To use the Cloudflare Edge Universal Orchestrator extension, you **must** create the CloudflareEdge Certificate Store Type. This only needs to happen _once_ per Keyfactor Command instance.
+
+
+
+
+
+
+
+
+#### Supported Operations
+
+| Operation | Is Supported |
+|--------------|------------------------------------------------------------------------------------------------------------------------|
+| Add | 🔲 Unchecked |
+| Remove | 🔲 Unchecked |
+| Discovery | 🔲 Unchecked |
+| Reenrollment | 🔲 Unchecked |
+| Create | 🔲 Unchecked |
+
+#### Store Type Creation
+
+##### Using kfutil:
+`kfutil` is a custom CLI for the Keyfactor Command API and can be used to create certificate store types.
+For more information on [kfutil](https://github.com/Keyfactor/kfutil) check out the [docs](https://github.com/Keyfactor/kfutil?tab=readme-ov-file#quickstart)
+ Click to expand CloudflareEdge kfutil details
+
+ ##### Using online definition from GitHub:
+ This will reach out to GitHub and pull the latest store-type definition
+ ```shell
+ # Cloudflare Edge
+ kfutil store-types create CloudflareEdge
+ ```
+
+ ##### Offline creation using integration-manifest file:
+ If required, it is possible to create store types from the [integration-manifest.json](./integration-manifest.json) included in this repo.
+ You would first download the [integration-manifest.json](./integration-manifest.json) and then run the following command
+ in your offline environment.
+ ```shell
+ kfutil store-types create --from-file integration-manifest.json
+ ```
+
+
+
+#### Manual Creation
+Below are instructions on how to create the CloudflareEdge store type manually in
+the Keyfactor Command Portal
+ Click to expand manual CloudflareEdge details
+
+ Create a store type called `CloudflareEdge` with the attributes in the tables below:
+
+ ##### Basic Tab
+ | Attribute | Value | Description |
+ | --------- | ----- | ----- |
+ | Name | Cloudflare Edge | Display name for the store type (may be customized) |
+ | Short Name | CloudflareEdge | Short display name for the store type |
+ | Capability | CloudflareEdge | Store type name orchestrator will register with. Check the box to allow entry of value |
+ | Supports Add | 🔲 Unchecked | Indicates that the Store Type supports Management Add |
+ | Supports Remove | 🔲 Unchecked | Indicates that the Store Type supports Management Remove |
+ | Supports Discovery | 🔲 Unchecked | Indicates that the Store Type supports Discovery |
+ | Supports Reenrollment | 🔲 Unchecked | Indicates that the Store Type supports Reenrollment |
+ | Supports Create | 🔲 Unchecked | Indicates that the Store Type supports store creation |
+ | Needs Server | ✅ Checked | Determines if a target server name is required when creating store |
+ | Blueprint Allowed | 🔲 Unchecked | Determines if store type may be included in an Orchestrator blueprint |
+ | Uses PowerShell | 🔲 Unchecked | Determines if underlying implementation is PowerShell |
+ | Requires Store Password | 🔲 Unchecked | Enables users to optionally specify a store password when defining a Certificate Store. |
+ | Supports Entry Password | 🔲 Unchecked | Determines if an individual entry within a store can have a password. |
+
+ The Basic tab should look like this:
+
+ 
+
+ ##### Advanced Tab
+ | Attribute | Value | Description |
+ | --------- | ----- | ----- |
+ | Supports Custom Alias | Forbidden | Determines if an individual entry within a store can have a custom Alias. |
+ | Private Key Handling | Forbidden | This determines if Keyfactor can send the private key associated with a certificate to the store. Required because IIS certificates without private keys would be invalid. |
+ | PFX Password Style | Default | 'Default' - PFX password is randomly generated, 'Custom' - PFX password may be specified when the enrollment job is created (Requires the Allow Custom Password application setting to be enabled.) |
+
+ The Advanced tab should look like this:
+
+ 
+
+ > For Keyfactor **Command versions 24.4 and later**, a Certificate Format dropdown is available with PFX and PEM options. Ensure that **PFX** is selected, as this determines the format of new and renewed certificates sent to the Orchestrator during a Management job. Currently, all Keyfactor-supported Orchestrator extensions support only PFX.
+
+ ##### Custom Fields Tab
+ Custom fields operate at the certificate store level and are used to control how the orchestrator connects to the remote target server containing the certificate store to be managed. The following custom fields should be added to the store type:
+
+ | Name | Display Name | Description | Type | Default Value/Options | Required |
+ | ---- | ------------ | ---- | --------------------- | -------- | ----------- |
+
+ The Custom Fields tab should look like this:
+
+ 
+
+
+
+
+
+
+## Installation
+
+1. **Download the latest Cloudflare Edge Universal Orchestrator extension from GitHub.**
+
+ Navigate to the [Cloudflare Edge Universal Orchestrator extension GitHub version page](https://github.com/Keyfactor/cloudflare-edge-orchestrator/releases/latest). Refer to the compatibility matrix below to determine the asset should be downloaded. Then, click the corresponding asset to download the zip archive.
+
+ | Universal Orchestrator Version | Latest .NET version installed on the Universal Orchestrator server | `rollForward` condition in `Orchestrator.runtimeconfig.json` | `cloudflare-edge-orchestrator` .NET version to download |
+ | --------- | ----------- | ----------- | ----------- |
+ | Older than `11.0.0` | | | `net6.0` |
+ | Between `11.0.0` and `11.5.1` (inclusive) | `net6.0` | | `net6.0` |
+ | Between `11.0.0` and `11.5.1` (inclusive) | `net8.0` | `Disable` | `net6.0` || Between `11.0.0` and `11.5.1` (inclusive) | `net8.0` | `LatestMajor` | `net8.0` |
+ | `11.6` _and_ newer | `net8.0` | | `net8.0` |
+
+ Unzip the archive containing extension assemblies to a known location.
+
+ > **Note** If you don't see an asset with a corresponding .NET version, you should always assume that it was compiled for `net6.0`.
+
+2. **Locate the Universal Orchestrator extensions directory.**
+
+ * **Default on Windows** - `C:\Program Files\Keyfactor\Keyfactor Orchestrator\extensions`
+ * **Default on Linux** - `/opt/keyfactor/orchestrator/extensions`
+
+3. **Create a new directory for the Cloudflare Edge Universal Orchestrator extension inside the extensions directory.**
+
+ Create a new directory called `cloudflare-edge-orchestrator`.
+ > The directory name does not need to match any names used elsewhere; it just has to be unique within the extensions directory.
+
+4. **Copy the contents of the downloaded and unzipped assemblies from __step 2__ to the `cloudflare-edge-orchestrator` directory.**
+
+5. **Restart the Universal Orchestrator service.**
+
+ Refer to [Starting/Restarting the Universal Orchestrator service](https://software.keyfactor.com/Core-OnPrem/Current/Content/InstallingAgents/NetCoreOrchestrator/StarttheService.htm).
+
+
+
+> The above installation steps can be supplemented by the [official Command documentation](https://software.keyfactor.com/Core-OnPrem/Current/Content/InstallingAgents/NetCoreOrchestrator/CustomExtensions.htm?Highlight=extensions).
+
+
+
+## Defining Certificate Stores
+
+
+
+### Store Creation
+
+#### Manually with the Command UI
+
+Click to expand details
+
+1. **Navigate to the _Certificate Stores_ page in Keyfactor Command.**
+
+ Log into Keyfactor Command, toggle the _Locations_ dropdown, and click _Certificate Stores_.
+
+2. **Add a Certificate Store.**
+
+ Click the Add button to add a new Certificate Store. Use the table below to populate the **Attributes** in the **Add** form.
+
+ | Attribute | Description |
+ | --------- |---------------------------------------------------------|
+ | Category | Select "Cloudflare Edge" or the customized certificate store name from the previous step. |
+ | Container | Optional container to associate certificate store with. |
+ | Client Machine | The account identifier for the Cloudflare account to be used for connecting to the Cloudflare API. |
+ | Store Path | The zone identifier for the Cloudflare zone where the edge certificates are located. |
+ | Orchestrator | Select an approved orchestrator capable of managing `CloudflareEdge` certificates. Specifically, one with the `CloudflareEdge` capability. |
+
+
+
+
+
+#### Using kfutil CLI
+
+Click to expand details
+
+1. **Generate a CSV template for the CloudflareEdge certificate store**
+
+ ```shell
+ kfutil stores import generate-template --store-type-name CloudflareEdge --outpath CloudflareEdge.csv
+ ```
+2. **Populate the generated CSV file**
+
+ Open the CSV file, and reference the table below to populate parameters for each **Attribute**.
+
+ | Attribute | Description |
+ | --------- | ----------- |
+ | Category | Select "Cloudflare Edge" or the customized certificate store name from the previous step. |
+ | Container | Optional container to associate certificate store with. |
+ | Client Machine | The account identifier for the Cloudflare account to be used for connecting to the Cloudflare API. |
+ | Store Path | The zone identifier for the Cloudflare zone where the edge certificates are located. |
+ | Orchestrator | Select an approved orchestrator capable of managing `CloudflareEdge` certificates. Specifically, one with the `CloudflareEdge` capability. |
+
+3. **Import the CSV file to create the certificate stores**
+
+ ```shell
+ kfutil stores import csv --store-type-name CloudflareEdge --file CloudflareEdge.csv
+ ```
+
+
+
+
+
+> The content in this section can be supplemented by the [official Command documentation](https://software.keyfactor.com/Core-OnPrem/Current/Content/ReferenceGuide/Certificate%20Stores.htm?Highlight=certificate%20store).
+
+
+
+
+## Configuring the Certificate Store
+
+When setting up your certificate store, you will be required to fill in the following properties on your certificate store:
+
+|Name|Value|
+|--|--|
+|Client Machine|Account ID|
+|Store Path|Zone ID|
+|Server Username||
+|Server Password|Either your Account API Token or User API Token|
+
+You can find your account ID and zone ID on the Cloudflare dashboard, located under your Account. Please refer to the [Cloudflare documentation](https://developers.cloudflare.com/fundamentals/account/find-account-and-zone-ids/) for more information.
+
+
+
+
+## License
+
+Apache License 2.0, see [LICENSE](LICENSE).
+
+## Related Integrations
+
+See all [Keyfactor Universal Orchestrator extensions](https://github.com/orgs/Keyfactor/repositories?q=orchestrator).
\ No newline at end of file
diff --git a/README.md.tpl b/README.md.tpl
deleted file mode 100644
index 383563f..0000000
--- a/README.md.tpl
+++ /dev/null
@@ -1,96 +0,0 @@
-# {{ name }}
-## {{ integration_type | capitalize }}
-
-{{ description }}
-
-
-***
-**Cloudflare Orchestrator Configuration**
-
-**Overview**
-
-
-
-This agent implements three job types – Inventory, Management Add, and Management Remove. Below are the steps necessary to configure this AnyAgent.
-
-
-**1. Create the New Certificate Store Type for the Cloudflare Orchestrator**
-
-In Keyfactor Command create a new Certificate Store Type similar to the one below:
-
-#### STORE TYPE CONFIGURATION
-CONFIG ELEMENT | DESCRIPTION
-------------------|------------------
-Name |Descriptive name for the Store Type
-Short Name |The short name that identifies the registered functionality of the orchestrator. Must be IISWBin
-Custom Capability|Store type name orchestrator will register with. Must be "IISBindings".
-Needs Server |Must be checked
-Blueprint Allowed |Unchecked
-Requires Store Password |Determines if a store password is required when configuring an individual store. This must be unchecked.
-Supports Entry Password |Determined if an individual entry within a store can have a password. This must be unchecked.
-Supports Custom Alias |Determines if an individual entry within a store can have a custom Alias. This must be Forbidden.
-Uses PowerShell |Unchecked
-Store Path Type |Determines what restrictions are applied to the store path field when configuring a new store. This must be Multiple Choice
-Store Path Value|A comma separated list of options to select from for the Store Path. This, combined with the hostname, will determine the location used for the certificate store management and inventory. Must be My, WebHosting
-Private Keys |This determines if Keyfactor can send the private key associated with a certificate to the store. This is required since IIS will need the private key material to establish TLS connections.
-PFX Password Style |This determines how the platform generate passwords to protect a PFX enrollment job that is delivered to the store. This can be either Default (system generated) or Custom (user determined).
-Job Types |Inventory, Add, and Remove are the supported job types.
-
-
-**Advanced Settings:**
-
-
-**Custom Fields:**
-
-
-
-Parameter Name|Parameter Type|Default Value|Required
----|---|---|---
-spnwithport|Boolean|false|No
-
-
-**Entry Parameters:**
-This section must be configured with binding fields. The parameters will be populated with the appropriate data when creating a new certificate store.
-
-- **Site Name** – Required (Adding an entry, Removing an entry, Reenrolling an entry). The site name for the web site being bound to – i.e. "Default Web Site"
-- **IP Address** – Required (Adding an entry, Removing an entry, Reenrolling an entry). The IP address for the web site being bound to. Default is "\*" for all IP Addresses.
-- **Port** – Required (Adding an entry, Removing an entry, Reenrolling an entry). The port for the web site being bound to. Default is "443".
-- **Host Name** – Optional. The host name for the web site being bound to.
-- **Protocol** - Required (Adding an entry, Removing an entry, Reenrolling an entry)
- - https
- - http
-- **Sni Flag** – Optional. Set the SNI flag associated with the binding being created. Default is "0". Acceptable values are:
- - 0 - No SNI
- - 1 - SNI Enabled
- - 2 - Non SNI Binding
- - 3 - SNI Binding
-
-Parameter Name|Parameter Type|Default Value|Required
----|---|---|---
-Port|String|443|Yes
-IP Address|String|*|Yes
-Host Name |String||No
-Site Name |String|Default Web Site|Yes
-Sni Flag |String|0 - No SNI|No
-Protocol |Multiple Choice|https|Yes
-
-
-
-**2. Register the Cloudflare Orchestrator with Keyfactor**
-See Keyfactor InstallingKeyfactorOrchestrators.pdf Documentation. Get from your Keyfactor contact/representative.
-
-**3. Create an Cloudflare Certificate Store within Keyfactor Command**
-
-In Keyfactor Command create a new Certificate Store similar to the one below, selecting IIS With Binding as the Category and the parameters as described in "Create the New Certificate Store Type for the New IIS-With-Bindings AnyAgent".
-
-
-
-#### STORE CONFIGURATION
-CONFIG ELEMENT |DESCRIPTION
-----------------|---------------
-Category |The type of certificate store to be configured. Select category based on the display name configured above.
-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 server to be managed. The Change Credentials option must be clicked to provide a username and password. This account will be used to manage the remote server via PowerShell.
-Store Path |My or WebHosting
-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.
\ No newline at end of file
diff --git a/docsource/cloudflare-account-id-zone-id.png b/docsource/cloudflare-account-id-zone-id.png
new file mode 100644
index 0000000..f67b348
Binary files /dev/null and b/docsource/cloudflare-account-id-zone-id.png differ
diff --git a/docsource/cloudflareedge.md b/docsource/cloudflareedge.md
new file mode 100644
index 0000000..0685dfd
--- /dev/null
+++ b/docsource/cloudflareedge.md
@@ -0,0 +1,3 @@
+## Overview
+
+
diff --git a/docsource/content.md b/docsource/content.md
new file mode 100644
index 0000000..0ce59f6
--- /dev/null
+++ b/docsource/content.md
@@ -0,0 +1,34 @@
+## Overview
+
+The Cloudflare Edge Orchestrator Extension is an integration that can inventory [Cloudflare Edge certificates](https://developers.cloudflare.com/ssl/concepts/#edge-certificate).
+
+## Requirements
+
+To inventory certificates, the Universal Orchestrator instance **must** be able to reach the server hosting the certificate over the network.
+Cloudflare's API does not provide the certificate contents, so the extension fetches the certificate directly from the server using a TLS handshake (via OpenSSL).
+
+### Authentication and Authorization
+
+When configuring the certificate store, the server password will contain the API token used to access the Cloudflare API. This can be either an **Account API Token** or a **User API Token**. See the [guide on how to create an API token](https://developers.cloudflare.com/fundamentals/api/get-started/create-token/).
+
+The API token must have the following permissions:
+
+|Permission|Required|Documentation|
+|--|--|--|
+|Account:SSL|Yes|[List Certificate Packs](https://developers.cloudflare.com/api/resources/ssl/subresources/certificate_packs/methods/list/)|
+|Certificates:Read|Yes|[List Certificate Packs](https://developers.cloudflare.com/api/resources/ssl/subresources/certificate_packs/methods/list/)|
+
+## Configuring the Certificate Store
+
+When setting up your certificate store, you will be required to fill in the following properties on your certificate store:
+
+|Name|Value|
+|--|--|
+|Client Machine|Account ID|
+|Store Path|Zone ID|
+|Server Username||
+|Server Password|Either your Account API Token or User API Token|
+
+You can find your account ID and zone ID on the Cloudflare dashboard, located under your Account. Please refer to the [Cloudflare documentation](https://developers.cloudflare.com/fundamentals/account/find-account-and-zone-ids/) for more information.
+
+
\ No newline at end of file
diff --git a/docsource/images/CloudflareEdge-advanced-store-type-dialog.png b/docsource/images/CloudflareEdge-advanced-store-type-dialog.png
new file mode 100644
index 0000000..ce89bb7
Binary files /dev/null and b/docsource/images/CloudflareEdge-advanced-store-type-dialog.png differ
diff --git a/docsource/images/CloudflareEdge-basic-store-type-dialog.png b/docsource/images/CloudflareEdge-basic-store-type-dialog.png
new file mode 100644
index 0000000..342b7b7
Binary files /dev/null and b/docsource/images/CloudflareEdge-basic-store-type-dialog.png differ
diff --git a/docsource/images/CloudflareEdge-custom-fields-store-type-dialog.png b/docsource/images/CloudflareEdge-custom-fields-store-type-dialog.png
new file mode 100644
index 0000000..ea975d3
Binary files /dev/null and b/docsource/images/CloudflareEdge-custom-fields-store-type-dialog.png differ
diff --git a/integration-manifest.json b/integration-manifest.json
index 4673202..b96e7b9 100644
--- a/integration-manifest.json
+++ b/integration-manifest.json
@@ -1,7 +1,50 @@
{
- "$schema": "https://keyfactor.github.io/integration-manifest-schema.json",
+ "$schema": "https://keyfactor.github.io/v2/integration-manifest-schema.json",
"integration_type": "orchestrator",
- "name": "Cloudflare Orchestrator",
- "status": "Development",
- "description": ""
+ "name": "Cloudflare Edge Orchestrator",
+ "status": "production",
+ "support_level": "kf-supported",
+ "update_catalog": true,
+ "link_github": false,
+ "release_project": "Cloudflare/Cloudflare.csproj",
+ "release_dir": "Cloudflare/bin/Release",
+ "description": "The Cloudflare Edge Orchestrator integration enables Keyfactor to inventory SSL/TLS certificates from Cloudflare's edge network.",
+ "about": {
+ "orchestrator": {
+ "UOFramework": "11.0",
+ "keyfactor_platform_version": "11.0",
+ "store_types": [
+ {
+ "Name": "Cloudflare Edge",
+ "ShortName": "CloudflareEdge",
+ "Capability": "CloudflareEdge",
+ "LocalStore": false,
+ "SupportedOperations": {
+ "Add": false,
+ "Create": false,
+ "Discovery": false,
+ "Enrollment": false,
+ "Remove": false
+ },
+ "EntryParameters": [],
+ "StorePathType": "",
+ "StorePathValue": "",
+ "PrivateKeyAllowed": "Forbidden",
+ "ClientMachineDescription": "The account identifier for the Cloudflare account to be used for connecting to the Cloudflare API.",
+ "StorePathDescription": "The zone identifier for the Cloudflare zone where the edge certificates are located.",
+ "JobProperties": [],
+ "ServerRequired": true,
+ "PowerShell": false,
+ "BlueprintAllowed": false,
+ "CustomAliasAllowed": "Forbidden",
+ "Properties": [],
+ "PasswordOptions": {
+ "EntrySupported": false,
+ "StoreRequired": false,
+ "Style": "Default"
+ }
+ }
+ ]
+ }
+ }
}
\ No newline at end of file