You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+30Lines changed: 30 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -312,6 +312,12 @@ The F5 Universal Orchestrator extension implements 3 Certificate Store Types. De
312
312
Refer to [Starting/Restarting the Universal Orchestrator service](https://software.keyfactor.com/Core-OnPrem/Current/Content/InstallingAgents/NetCoreOrchestrator/StarttheService.htm).
313
313
314
314
315
+
6. **(optional) PAM Integration**
316
+
317
+
The F5 Universal Orchestrator extension is compatible with all supported Keyfactor PAM extensions to resolve PAM-eligible secrets. PAM extensions running on Universal Orchestrators enable secure retrieval of secrets from a connected PAM provider.
318
+
319
+
To configure a PAM provider, [reference the Keyfactor Integration Catalog](https://keyfactor.github.io/integrations-catalog/content/pam) to selectan extension, and follow the associated instructions to install it on the Universal Orchestrator (remote).
320
+
315
321
316
322
> The above installation steps can be supplimented by the [official Command documentation](https://software.keyfactor.com/Core-OnPrem/Current/Content/InstallingAgents/NetCoreOrchestrator/CustomExtensions.htm?Highlight=extensions).
317
323
@@ -352,6 +358,19 @@ The F5 Universal Orchestrator extension implements 3 Certificate Store Types, ea
352
358
353
359
354
360
361
+
<details><summary>Attributes eligible for retrieval by a PAM Provider on the Universal Orchestrator</summary>
362
+
363
+
If a PAM provider was installed _on the Universal Orchestrator_ in the [Installation](#Installation) section, the following parameters can be configured for retrieval _on the Universal Orchestrator_.
364
+
| Attribute | Description |
365
+
| --------- | ----------- |
366
+
| Store Password | Check "No Password" if you wish the private key of any added certificate to be set to Key Security Type "Normal". Enter a value (either a password or pointer to an installed PAM provider key for the password) to be used to encrypt the private key of any added certificate for Key Security Type of "Password". |
367
+
368
+
Please refer to the **Universal Orchestrator (remote)** usage section ([PAM providers on the Keyfactor Integration Catalog](https://keyfactor.github.io/integrations-catalog/content/pam)) for your selected PAM provider for instructions on how to load attributes orchestrator-side.
369
+
370
+
> Any secret can be rendered by a PAM provider _installed on the Keyfactor Command server_. The above parameters are specific to attributes that can be fetched by an installed PAM provider running on the Universal Orchestrator server itself.
371
+
</details>
372
+
373
+
355
374
</details>
356
375
357
376
* **Using kfutil**
@@ -383,6 +402,17 @@ The F5 Universal Orchestrator extension implements 3 Certificate Store Types, ea
383
402
384
403
385
404
405
+
<details><summary>Attributes eligible for retrieval by a PAM Provider on the Universal Orchestrator</summary>
406
+
407
+
If a PAM provider was installed _on the Universal Orchestrator_ in the [Installation](#Installation) section, the following parameters can be configured for retrieval _on the Universal Orchestrator_.
408
+
| Attribute | Description |
409
+
| --------- | ----------- |
410
+
| Store Password | Check "No Password"if you wish the private key of any added certificate to be set to Key Security Type "Normal". Enter a value (either a password or pointer to an installed PAM provider key for the password) to be used to encrypt the private key of any added certificate for Key Security Type of "Password". |
411
+
412
+
> Any secret can be rendered by a PAM provider _installed on the Keyfactor Command server_. The above parameters are specific to attributes that can be fetched by an installed PAM provider running on the Universal Orchestrator server itself.
413
+
</details>
414
+
415
+
386
416
3. **Import the CSV file to create the certificate stores**
0 commit comments