From b5c4e1ec72de3687df5bf3e1e6a77df03b76c7be Mon Sep 17 00:00:00 2001 From: Morgan Gangwere Date: Tue, 10 Nov 2026 16:10:37 -0800 Subject: [PATCH 1/4] nudge manifest --- integration-manifest.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/integration-manifest.json b/integration-manifest.json index ce0bde7..746f421 100644 --- a/integration-manifest.json +++ b/integration-manifest.json @@ -2,8 +2,8 @@ "$schema": "https://keyfactor.github.io/integration-manifest-schema.json", "integration_type": "anyca-plugin", "name": "Nameshield AnyCA REST Gateway Plugin", - "status": "prototype", "support_level": "keyfactor", + "status": "prototype", "link_github": true, "update_catalog": true, "description": "Nameshield plugin for the AnyCA REST Gateway framework", @@ -38,4 +38,4 @@ ] } } -} \ No newline at end of file +} From 9ed1a284721f30b35faaa2b609e28fa6b5be1301 Mon Sep 17 00:00:00 2001 From: Morgan Gangwere Date: Tue, 10 Nov 2026 16:10:37 -0800 Subject: [PATCH 2/4] nudge manifest --- integration-manifest.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/integration-manifest.json b/integration-manifest.json index ce0bde7..746f421 100644 --- a/integration-manifest.json +++ b/integration-manifest.json @@ -2,8 +2,8 @@ "$schema": "https://keyfactor.github.io/integration-manifest-schema.json", "integration_type": "anyca-plugin", "name": "Nameshield AnyCA REST Gateway Plugin", - "status": "prototype", "support_level": "keyfactor", + "status": "prototype", "link_github": true, "update_catalog": true, "description": "Nameshield plugin for the AnyCA REST Gateway framework", @@ -38,4 +38,4 @@ ] } } -} \ No newline at end of file +} From 8a2e082d11742cccca7d1f6a5b05a05d3d9bfad0 Mon Sep 17 00:00:00 2001 From: Morgan Gangwere Date: Tue, 10 Nov 2026 16:18:57 -0800 Subject: [PATCH 3/4] fix incorrect key --- integration-manifest.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/integration-manifest.json b/integration-manifest.json index 746f421..c4a7508 100644 --- a/integration-manifest.json +++ b/integration-manifest.json @@ -2,7 +2,7 @@ "$schema": "https://keyfactor.github.io/integration-manifest-schema.json", "integration_type": "anyca-plugin", "name": "Nameshield AnyCA REST Gateway Plugin", - "support_level": "keyfactor", + "support_level": "kf-supported", "status": "prototype", "link_github": true, "update_catalog": true, From 4ef454dfa0a1d80f0bb20eae220570f9ff6887c8 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Wed, 11 Nov 2026 00:19:34 +0000 Subject: [PATCH 4/4] docs: auto-generate README and documentation [skip ci] --- README.md | 24 ++++++++++-------------- 1 file changed, 10 insertions(+), 14 deletions(-) diff --git a/README.md b/README.md index 0bfb158..717daa7 100644 --- a/README.md +++ b/README.md @@ -14,7 +14,7 @@ Support - + ยท Requirements @@ -33,7 +33,6 @@

- The Nameshield AnyCA Gateway REST plugin extends the capabilities of Nameshield CA to Keyfactor Command via the Keyfactor AnyCA Gateway REST. The plugin represents a fully featured AnyCA REST Plugin with the following capabilies: * SSL Certificate Synchronization * All Sync jobs are currently treated as a full sync @@ -46,7 +45,7 @@ The Nameshield AnyCA Gateway REST plugin extends the capabilities of Nameshield The Nameshield AnyCA Gateway REST plugin is compatible with the Keyfactor AnyCA Gateway REST 24.2.0 and later. ## Support -The Nameshield AnyCA Gateway REST plugin is open source and community supported, meaning that there is **no SLA** applicable. +The Nameshield AnyCA Gateway REST plugin 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](../../issues)** tab. If you want to contribute actual bug fixes or proposed enhancements, use the **[Pull requests](../../pulls)** tab. @@ -60,16 +59,15 @@ TODO Requirements is a required section 2. On the server hosting the AnyCA Gateway REST, download and unzip the latest [Nameshield AnyCA Gateway REST plugin](https://github.com/Keyfactor/nameshield-caplugin/releases/latest) from GitHub. -3. Copy the unzipped directory (usually called `net6.0` or `net8.0`) to the Extensions directory: +3. Copy the unzipped directory (usually called `net6.0`) to the Extensions directory: ```shell Depending on your AnyCA Gateway REST version, copy the unzipped directory to one of the following locations: Program Files\Keyfactor\AnyCA Gateway\AnyGatewayREST\net6.0\Extensions - Program Files\Keyfactor\AnyCA Gateway\AnyGatewayREST\net8.0\Extensions ``` - > The directory containing the Nameshield AnyCA Gateway REST plugin DLLs (`net6.0` or `net8.0`) can be named anything, as long as it is unique within the `Extensions` directory. + > The directory containing the Nameshield AnyCA Gateway REST plugin DLLs (`net6.0`) can be named anything, as long as it is unique within the `Extensions` directory. 4. Restart the AnyCA Gateway REST service. @@ -87,9 +85,9 @@ TODO Requirements is a required section Populate using the configuration fields collected in the [requirements](#requirements) section. - * **ApiUrl** - The base URL to send API requests to. Standard URLs are https://api.nameshield.net/ for production environment, and https://ote-api.nameshield.net/ for test and development - * **ApiToken** - The Bearer token to use to authenticate to the Nameshield API - * **Enabled** - Flag to Enable or Disable gateway functionality. Diabling is primarily used to allow creation of the CA prior to configuration information being available. + * **ApiUrl** - The base URL to send API requests to. Standard URLs are https://api.nameshield.net/ for production environment, and https://ote-api.nameshield.net/ for test and development + * **ApiToken** - The Bearer token to use to authenticate to the Nameshield API + * **Enabled** - Flag to Enable or Disable gateway functionality. Diabling is primarily used to allow creation of the CA prior to configuration information being available. 2. When defining templates, use the product names as the ProductID (e.g. Digicert Secure Site EV) as opposed to the ID (e.g. ABC012) @@ -97,10 +95,8 @@ TODO Requirements is a required section 4. In Keyfactor Command (v12.3+), for each imported Certificate Template, follow the [official documentation](https://software.keyfactor.com/Core-OnPrem/Current/Content/ReferenceGuide/Configuring%20Template%20Options.htm) to define enrollment fields for each of the following parameters: - * **OrganizationId** - If you know your organization's ID in nameshield, you can supply that here and that will be used as the organization regardless of what values exist in the request or the Organization field - * **Organization** - If OrganizationId is empty, and an organization name is provided here, the Nameshield gateway will use that name to do organization lookups when enrolling. If neither OrganizationId nor Organization is supplied, the gateway will use whatever is in the O= field of the request subject. - - + * **OrganizationId** - If you know your organization's ID in nameshield, you can supply that here and that will be used as the organization regardless of what values exist in the request or the Organization field + * **Organization** - If OrganizationId is empty, and an organization name is provided here, the Nameshield gateway will use that name to do organization lookups when enrolling. If neither OrganizationId nor Organization is supplied, the gateway will use whatever is in the O= field of the request subject. ## License @@ -108,4 +104,4 @@ Apache License 2.0, see [LICENSE](LICENSE). ## Related Integrations -See all [Keyfactor Any CA Gateways (REST)](https://github.com/orgs/Keyfactor/repositories?q=anycagateway). \ No newline at end of file +See all [Keyfactor Any CA Gateways (REST)](https://github.com/orgs/Keyfactor/repositories?q=anycagateway).