From 908daea048a33eb3b498a21efcea30fbc27eb390 Mon Sep 17 00:00:00 2001 From: Rex Wheeler Date: Mon, 14 Aug 2023 16:29:25 -0700 Subject: [PATCH 1/2] Publish in catalog --- integration-manifest.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/integration-manifest.json b/integration-manifest.json index 5ebafdf..4cd986d 100644 --- a/integration-manifest.json +++ b/integration-manifest.json @@ -4,8 +4,8 @@ "name": "DataPower Orchestrator", "status": "production", "description": "The IBM DataPower Orchestrator allows for the management of certificates in the IBM Datapower platform. Inventory, Add and Remove functions are supported. This integration can add/replace certificates in any domain\\directory combination. ", - "link_github": false, - "update_catalog": false, + "link_github": true, + "update_catalog": true, "about": { "orchestrator": { "UOFramework": "10.1", From 28c325417de9a4bb67b3ee521b674fa172c353cc Mon Sep 17 00:00:00 2001 From: Keyfactor Date: Mon, 14 Aug 2023 23:29:56 +0000 Subject: [PATCH 2/2] Update generated README --- README.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 42037ab..aaae0bc 100644 --- a/README.md +++ b/README.md @@ -4,6 +4,7 @@ The IBM DataPower Orchestrator allows for the management of certificates in the #### Integration status: Production - Ready for use in production environments. + ## About the Keyfactor Universal Orchestrator Extension 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. @@ -15,6 +16,7 @@ The Universal Orchestrator is the successor to the Windows Orchestrator. This Or + --- @@ -53,6 +55,11 @@ It is not necessary to use a PAM Provider for all of the secrets available above If a PAM Provider will be used for one of the fields above, start by referencing the [Keyfactor Integration Catalog](https://keyfactor.github.io/integrations-catalog/content/pam). 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 +

+ + + ### Example PAM Provider Setup 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](https://keyfactor.github.io/integrations-catalog/content/pam) on the Universal Orchestrator. @@ -79,7 +86,8 @@ To have the __Server Password__ field resolved by the `Hashicorp-Vault` provider ~~~ 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. - +

+