From 2de9c16bda9c2ffddfd02780fc477cdf43282795 Mon Sep 17 00:00:00 2001 From: Michael Henderson Date: Wed, 7 Dec 2022 12:41:48 -0800 Subject: [PATCH 1/2] replace tab with spaces --- integration-manifest.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/integration-manifest.json b/integration-manifest.json index 72177f4..2cf1679 100644 --- a/integration-manifest.json +++ b/integration-manifest.json @@ -8,7 +8,7 @@ "about": { "orchestrator": { "UOFramework": "10.1", - "pam_support": true, + "pam_support": true, "win": { "supportsCreateStore": false, "supportsDiscovery": false, From 8f55a1472e51c858a01b4a659a55810e57232e20 Mon Sep 17 00:00:00 2001 From: Keyfactor Date: Wed, 7 Dec 2022 20:42:30 +0000 Subject: [PATCH 2/2] Update generated README --- README.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/README.md b/README.md index bf27cb1..a7fb17d 100644 --- a/README.md +++ b/README.md @@ -37,6 +37,20 @@ The Keyfactor Universal Orchestrator may be installed on either Windows or Linux |Supports Inventory|✓ | | +## PAM Integration + +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| +|----|-----------| +|Server UserName|The user id that will be used to authenticate into the server hosting the store| +|Server Password|The password that will be used to authenticate into the server hosting the store| +It is not necessary to implement all of the secrets available to be managed by a PAM provider. For each value that you want managed by a PAM provider, simply enter the key value inside your specific PAM provider that will hold this value into the corresponding field when setting up the certificate store, discovery job, or API call. + +Setting up a PAM provider for use involves adding an additional section to the manifest.json file for this extension as well as setting up the PAM provider you will be using. Each of these steps is specific to the PAM provider you will use and are documented in the specific GitHub repo for that provider. For a list of Keyfactor supported PAM providers, please reference the [Keyfactor Integration Catalog](https://keyfactor.github.io/integrations-catalog/content/pam). + ---