From 3a600fbb124ee3a1cf54a6e2528522d8b7ac8e9e Mon Sep 17 00:00:00 2001 From: Hayden Roszell Date: Wed, 3 Jul 2024 20:27:09 +0100 Subject: [PATCH] chore(manifest): Re-create description fields in manifest to use Noun Phrase Style --- docs/fortigate.md | 4 ++-- integration-manifest.json | 24 ++++-------------------- 2 files changed, 6 insertions(+), 22 deletions(-) diff --git a/docs/fortigate.md b/docs/fortigate.md index 8c291f8..752845c 100644 --- a/docs/fortigate.md +++ b/docs/fortigate.md @@ -101,8 +101,8 @@ The following table describes the required and optional fields for the `Fortigat | --------- | ----------- | ------------------------- | | Category | Select "Fortigate" or the customized certificate store name from the previous step. | | | Container | Optional container to associate certificate store with. | | -| Client Machine | For the Client Machine field, enter the IP address or DNS name of your Fortigate server. Example: '192.168.1.1' or 'fortigate.domain.com'. | | -| Store Path | For the Store Path field, enter any value as it is not used in this integration. Example: 'NotApplicable'. | | +| Client Machine | The IP address or DNS name of the Fortigate server. For example, '192.168.1.1' or 'fortigate.example.com'. | | +| Store Path | Any arbitrary value, as the Store Path field is not used in the Fortigate integration. For example, 'defaultStorePath'. | | | Orchestrator | Select an approved orchestrator capable of managing `Fortigate` certificates. Specifically, one with the `Fortigate` capability. | | * **Using kfutil** diff --git a/integration-manifest.json b/integration-manifest.json index afdda45..6879213 100644 --- a/integration-manifest.json +++ b/integration-manifest.json @@ -1,9 +1,9 @@ { - "$schema": "/Users/hroszell/coding/dev/staff-tools/keyfactor.github.io/v2/integration-manifest-schema.json", + "$schema": "https://keyfactor.github.io/v2/integration-manifest-schema.json", "integration_type": "orchestrator", "name": "Fortigate", "status": "production", - "description": "This integration is used to inventory and manage certificates in Fortigate.", + "description": "The Fortigate Universal Orchestrator extension enables remote management of cryptographic certificates on Fortigate devices, including inventory, addition, and removal of certificates.", "link_github": true, "support_level": "kf-supported", "update_catalog": true, @@ -11,22 +11,6 @@ "orchestrator": { "UOFramework": "10.1", "pam_support": true, - "win": { - "supportsCreateStore": false, - "supportsDiscovery": false, - "supportsManagementAdd": true, - "supportsManagementRemove": true, - "supportsReenrollment": false, - "supportsInventory": true - }, - "linux": { - "supportsCreateStore": false, - "supportsDiscovery": false, - "supportsManagementAdd": true, - "supportsManagementRemove": true, - "supportsReenrollment": false, - "supportsInventory": true - }, "store_types": [ { "Name": "Fortigate", @@ -51,8 +35,8 @@ }, "Properties": [], "EntryParameters": [], - "ClientMachineDescription": "For the Client Machine field, enter the IP address or DNS name of your Fortigate server. Example: '192.168.1.1' or 'fortigate.domain.com'.", - "StorePathDescription": "For the Store Path field, enter any value as it is not used in this integration. Example: 'NotApplicable'." + "ClientMachineDescription": "The IP address or DNS name of the Fortigate server. For example, '192.168.1.1' or 'fortigate.example.com'.", + "StorePathDescription": "Any arbitrary value, as the Store Path field is not used in the Fortigate integration. For example, 'defaultStorePath'." } ] }