+ Dell iDRAC Universal Orchestrator Extension +
+ +
+
+
+ + + Support + + · + + Installation + + · + + License + + · + + Related Integrations + +
-Certificate inventory and management for Integrated Dell Remote Access Controller appliances +## Overview -#### Integration status: Production - Ready for use in production environments. +The Integrated Dell Remote Access Controller (iDRAC) Orchestrator Extension supports the following use cases: -## About the Keyfactor Universal Orchestrator Extension +- Inventorying the iDRAC instance's server certificate and importing it into Keyfactor Command for management +- Adding or Replacing an existing or newly enrolled certificate and private key to an existing iDRAC instance. To replace an existing server certificate, the Ovewrite flag in Keyfactor Command must be selected. -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. +Use cases NOT supported by the iDRAC Orchestrator Extension: -The Universal Orchestrator is part of the Keyfactor software distribution and is available via the Keyfactor customer portal. For general instructions on installing Extensions, see the “Keyfactor Command Orchestrator Installation and Configuration Guide” section of the Keyfactor documentation. For configuration details of this specific Extension see below in this readme. +- Removing a server certificate from an iDRAC instance. +- Inventorying or Managing any other certificate type on an iDRAC intance. -The Universal Orchestrator is the successor to the Windows Orchestrator. This Orchestrator Extension plugin only works with the Universal Orchestrator and does not work with the Windows Orchestrator. +Special Notes: +* When adding or replacing the server certificate, there will be a few minute delay as the iDRAC instance will restart. As a result, it may take a few minutes before the new certificate is reflected in subsequent Inventory jobs. +* When replacing an existing server certificate, the Overwrite checkbox must be selected/checked. When this checkbox is selected, Keyfactor Command may require you to enter an alias. This alias is not used by the orchestrator extension, so just enter any value. -## Support for Dell iDRAC Orchestrator -Dell iDRAC Orchestrator 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. +## Compatibility ---- +This integration is compatible with Keyfactor Universal Orchestrator version 10.4 and later. +## Support +The Dell iDRAC Universal Orchestrator extension is supported by Keyfactor for Keyfactor customers. If you have a support issue, please open a support ticket with your Keyfactor representative. 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. ---- +## Requirements & Prerequisites +Before installing the Dell iDRAC Universal Orchestrator extension, we recommend that you install [kfutil](https://github.com/Keyfactor/kfutil). Kfutil is a command-line tool that simplifies the process of creating store types, installing extensions, and instantiating certificate stores in Keyfactor Command. -## Keyfactor Version Supported +1. The Orchestrator must run on a Windows Server machine with the [Racadm CLI utility](https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=8gmf6) installed, configured to reach the target iDRAC instance. The Orchestrator must have read and write access to the folder where racadm.exe is installed. +2. A user id must be set up in iDRAC with minimum privileges of "Configure". This will be used by the Racadm utility to manage the store. -The minimum version of the Keyfactor Universal Orchestrator Framework needed to run this version of the extension is 10.4 -## Platform Specific Notes -The Keyfactor Universal Orchestrator may be installed on either Windows or Linux based platforms. The certificate operations supported by a capability may vary based what platform the capability is installed on. The table below indicates what capabilities are supported based on which platform the encompassing Universal Orchestrator is running. -| Operation | Win | Linux | -|-----|-----|------| -|Supports Management Add|✓ | | -|Supports Management Remove| | | -|Supports Create Store| | | -|Supports Discovery| | | -|Supports Reenrollment| | | -|Supports Inventory|✓ | | +## Create the iDRAC Certificate Store Type +To use the Dell iDRAC Universal Orchestrator extension, you **must** create the iDRAC Certificate Store Type. This only needs to happen _once_ per Keyfactor Command instance. -## 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: +* **Create iDRAC using kfutil**: -|Name|Description| -|----|-----------| -|ServerUsername|The user id that will be used to authenticate into the Dell Remote Access Controller| -|ServerPassword|The password that will be used to authenticate into the Dell Remote Access Controller| - + ```shell + # iDRAC + kfutil store-types create iDRAC + ``` -It is not necessary to use a PAM Provider for all of the secrets available above. If a PAM Provider should not be used, simply enter in the actual value to be used, as normal. +* **Create iDRAC manually in the Command UI**: +Create iDRAC manually in the Command UI
-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. + Create a store type called `iDRAC` with the attributes in the tables below: -General PAM Provider Configuration
-+ #### Basic Tab + | Attribute | Value | Description | + | --------- | ----- | ----- | + | Name | iDRAC | Display name for the store type (may be customized) | + | Short Name | iDRAC | Short display name for the store type | + | Capability | iDRAC | Store type name orchestrator will register with. Check the box to allow entry of value | + | Supports Add | ✅ Checked | Check the box. Indicates that the Store Type supports Management Add | + | Supports Remove | 🔲 Unchecked | Indicates that the Store Type supports Management Remove | + | Supports Discovery | 🔲 Unchecked | Indicates that the Store Type supports Discovery | + | Supports Reenrollment | 🔲 Unchecked | Indicates that the Store Type supports Reenrollment | + | Supports Create | 🔲 Unchecked | Indicates that the Store Type supports store creation | + | Needs Server | ✅ Checked | Determines if a target server name is required when creating store | + | Blueprint Allowed | ✅ Checked | Determines if store type may be included in an Orchestrator blueprint | + | Uses PowerShell | 🔲 Unchecked | Determines if underlying implementation is PowerShell | + | Requires Store Password | 🔲 Unchecked | Enables users to optionally specify a store password when defining a Certificate Store. | + | Supports Entry Password | 🔲 Unchecked | Determines if an individual entry within a store can have a password. | + The Basic tab should look like this: +  -### Example PAM Provider Setup + #### Advanced Tab + | Attribute | Value | Description | + | --------- | ----- | ----- | + | Supports Custom Alias | Forbidden | Determines if an individual entry within a store can have a custom Alias. | + | Private Key Handling | Required | This determines if Keyfactor can send the private key associated with a certificate to the store. Required because IIS certificates without private keys would be invalid. | + | PFX Password Style | Default | 'Default' - PFX password is randomly generated, 'Custom' - PFX password may be specified when the enrollment job is created (Requires the Allow Custom Password application setting to be enabled.) | -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. + The Advanced tab should look like this: -Next, complete configuration of the PAM Provider on the UO by editing the `manifest.json` of the __PAM Provider__ (e.g. located at extensions/Hashicorp-Vault/manifest.json). The "initialization" parameters need to be entered here: +  -~~~ json - "Keyfactor:PAMProviders:Hashicorp-Vault:InitializationInfo": { - "Host": "http://127.0.0.1:8200", - "Path": "v1/secret/data", - "Token": "xxxxxx" - } -~~~ + #### Custom Fields Tab + Custom fields operate at the certificate store level and are used to control how the orchestrator connects to the remote target server containing the certificate store to be managed. The following custom fields should be added to the store type: -After these values are entered, the Orchestrator needs to be restarted to pick up the configuration. Now the PAM Provider can be used on other Orchestrator Extensions. + | Name | Display Name | Description | Type | Default Value/Options | Required | + | ---- | ------------ | ---- | --------------------- | -------- | ----------- | + | ServerUsername | Server Username | The user ID (or, if using a PAM provider, the key pointing to the user ID) to log into the iDRAC instance being managed. | Secret | | 🔲 Unchecked | + | ServerPassword | Server Password | The password (or, if using a PAM provider, the key pointing to the password) for the user ID above. | Secret | | 🔲 Unchecked | -### Use the PAM Provider -With the PAM Provider configured as an extenion on the UO, a `json` object can be passed instead of an actual value to resolve the field with a PAM Provider. Consult the [Keyfactor Integration Catalog](https://keyfactor.github.io/integrations-catalog/content/pam) for the specific format of the `json` object. + The Custom Fields tab should look like this: -To have the __Server Password__ field resolved by the `Hashicorp-Vault` provider, the corresponding `json` object from the `Hashicorp-Vault` extension needs to be copied and filed in with the correct information: +  -~~~ json -{"Secret":"my-kv-secret","Key":"myServerPassword"} -~~~ -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. -
-Create Certificate Stores manually in the UI
-## iDRAC Orchestrator Extension Installation + 1. **Navigate to the _Certificate Stores_ page in Keyfactor Command.** -1. Stop the Keyfactor Universal Orchestrator Service. -2. In the Keyfactor Orchestrator installation folder (by convention usually C:\Program Files\Keyfactor\Keyfactor Orchestrator), find the "extensions" folder. Underneath that, create a new folder named DellIdrac or another name of your choosing. -3. Download the latest version of the iDRAC Orchestrator Extension from [GitHub](https://github.com/Keyfactor/dell-idrac-orchestrator). -4. Copy the contents of the download installation zip file into the folder created in step 2. -5. Start the Keyfactor Universal Orchestrator Service. -6. In Keyfactor Command, under Orchestrators => Management, approve the orchestrator you just installed the extension on. + Log into Keyfactor Command, toggle the _Locations_ dropdown, and click _Certificate Stores_. + 2. **Add a Certificate Store.** -## iDRAC Orchestrator Extension Configuration + Click the Add button to add a new Certificate Store. Use the table below to populate the **Attributes** in the **Add** form. + | Attribute | Description | + | --------- | ----------- | + | Category | Select "iDRAC" or the customized certificate store name from the previous step. | + | Container | Optional container to associate certificate store with. | + | Client Machine | The IP address of the iDRAC instance being managed. | + | Store Path | Enter the full path where the Racadm executable is installed on the orchestrator server. See [Requirements & Prerequisites](#requirements-&-prerequisites) above for more details. | + | Orchestrator | Select an approved orchestrator capable of managing `iDRAC` certificates. Specifically, one with the `iDRAC` capability. | + | ServerUsername | The user ID (or, if using a PAM provider, the key pointing to the user ID) to log into the iDRAC instance being managed. | + | ServerPassword | The password (or, if using a PAM provider, the key pointing to the password) for the user ID above. | -### Create an iDRAC Certificate Store Type -In Keyfactor Command, create a new certificate store type by navigating to Settings (the "gear" icon in the top right) => Certificate Store Types, and clicking ADD. Then enter the following information: + -
-
-
+ Basic Tab
+Attributes eligible for retrieval by a PAM Provider on the Universal Orchestrator
-- **Name** – Required. The descriptive display name of the new Certificate Store Type. Suggested => iDRAC -- **Short Name** – Required. This value ***must be*** iDRAC. -- **Custom Capability** - Leave unchecked -- **Supported Job Types** – Select Inventory and Add. -- **General Settings** - Select Needs Server. Select Blueprint Allowed if you plan to use blueprinting. Leave Uses PowerShell unchecked. -- **Password Settings** - Leave both options unchecked + 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_. + | Attribute | Description | + | --------- | ----------- | + | ServerUsername | The user ID (or, if using a PAM provider, the key pointing to the user ID) to log into the iDRAC instance being managed. | + | ServerPassword | The password (or, if using a PAM provider, the key pointing to the password) for the user ID above. | -
-
+
-Advanced Tab
+ 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. -- **Store Path Type** - Select Freeform -- **Supports Custom Alias** - Forbidden -- **Private Key Handling** - Required -- **PFX Password Style** - Default + > 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. +
-
+ Open the CSV file, and reference the table below to populate parameters for each **Attribute**.
+ | Attribute | Description |
+ | --------- | ----------- |
+ | Category | Select "iDRAC" or the customized certificate store name from the previous step. |
+ | Container | Optional container to associate certificate store with. |
+ | Client Machine | The IP address of the iDRAC instance being managed. |
+ | Store Path | Enter the full path where the Racadm executable is installed on the orchestrator server. See [Requirements & Prerequisites](#requirements-&-prerequisites) above for more details. |
+ | Orchestrator | Select an approved orchestrator capable of managing `iDRAC` certificates. Specifically, one with the `iDRAC` capability. |
+ | ServerUsername | The user ID (or, if using a PAM provider, the key pointing to the user ID) to log into the iDRAC instance being managed. |
+ | ServerPassword | The password (or, if using a PAM provider, the key pointing to the password) for the user ID above. |
-
+
-- **Category** – Required. Select the Name you entered when creating the Certificate Store Type. Suggested value was iDRAC.
+ 3. **Import the CSV file to create the certificate stores**
-- **Container** – Optional. Select a container if utilized.
+ ```shell
+ kfutil stores import csv --store-type-name iDRAC --file iDRAC.csv
+ ```
+
-- **Client Machine** – Required. The IP address of the iDRAC instance being managed.
-
-- **Store Path** – Required. Enter the full path where the Racadm executable is installed on the Orchestrator server. See [Installation Prerequisites](#installation-prerequisites) for more details.
+> The content in this section can be supplimented by the [official Command documentation](https://software.keyfactor.com/Core-OnPrem/Current/Content/ReferenceGuide/Certificate%20Stores.htm?Highlight=certificate%20store).
-- **Orchestrator** – Required. Select the orchestrator you wish to use to manage this store
-- **Server Username/Password** - Required. The credentials used to log into the iDRAC instance being managed. These values for server login can be either:
-
- - UserId/Password
- - PAM provider information used to look up the UserId/Password credentials
- Please make sure the user id entered has "Configure" privileges on the iDRAC instance.
-- **Use SSL** - N/A. This value is not referenced in the iDRAC Orchestrator Extension.
-- **Inventory Schedule** – Set a schedule for running Inventory jobs or "none", if you choose not to schedule Inventory at this time.
+## License
-When creating cert store type manually, that store property names and entry parameter names are case sensitive
+Apache License 2.0, see [LICENSE](LICENSE).
+## Related Integrations
+See all [Keyfactor Universal Orchestrator extensions](https://github.com/orgs/Keyfactor/repositories?q=orchestrator).
\ No newline at end of file
diff --git a/docsource/content.md b/docsource/content.md
new file mode 100644
index 0000000..0cd4e0b
--- /dev/null
+++ b/docsource/content.md
@@ -0,0 +1,21 @@
+## Overview
+
+The Integrated Dell Remote Access Controller (iDRAC) Orchestrator Extension supports the following use cases:
+
+- Inventorying the iDRAC instance's server certificate and importing it into Keyfactor Command for management
+- Adding or Replacing an existing or newly enrolled certificate and private key to an existing iDRAC instance. To replace an existing server certificate, the Ovewrite flag in Keyfactor Command must be selected.
+
+Use cases NOT supported by the iDRAC Orchestrator Extension:
+
+- Removing a server certificate from an iDRAC instance.
+- Inventorying or Managing any other certificate type on an iDRAC intance.
+
+Special Notes:
+* When adding or replacing the server certificate, there will be a few minute delay as the iDRAC instance will restart. As a result, it may take a few minutes before the new certificate is reflected in subsequent Inventory jobs.
+* When replacing an existing server certificate, the Overwrite checkbox must be selected/checked. When this checkbox is selected, Keyfactor Command may require you to enter an alias. This alias is not used by the orchestrator extension, so just enter any value.
+
+
+## Requirements
+
+1. The Orchestrator must run on a Windows Server machine with the [Racadm CLI utility](https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=8gmf6) installed, configured to reach the target iDRAC instance. The Orchestrator must have read and write access to the folder where racadm.exe is installed.
+2. A user id must be set up in iDRAC with minimum privileges of "Configure". This will be used by the Racadm utility to manage the store.
\ No newline at end of file
diff --git a/docsource/idrac.md b/docsource/idrac.md
new file mode 100644
index 0000000..0aa5d83
--- /dev/null
+++ b/docsource/idrac.md
@@ -0,0 +1 @@
+## Overview
\ No newline at end of file
diff --git a/integration-manifest.json b/integration-manifest.json
index 2f55876..c5d64a5 100644
--- a/integration-manifest.json
+++ b/integration-manifest.json
@@ -8,27 +8,12 @@
"link_github": true,
"update_catalog": true,
"release_dir": "DellIdrac/bin/Release",
+ "release_project": "DellIdrac/DellIDRACOrchestrator.csproj",
"about": {
"orchestrator": {
"UOFramework": "10.4",
"keyfactor_platform_version": "10.3",
"pam_support": true,
- "win": {
- "supportsCreateStore": false,
- "supportsDiscovery": false,
- "supportsManagementAdd": true,
- "supportsManagementRemove": false,
- "supportsReenrollment": false,
- "supportsInventory": true
- },
- "linux": {
- "supportsCreateStore": false,
- "supportsDiscovery": false,
- "supportsManagementAdd": false,
- "supportsManagementRemove": false,
- "supportsReenrollment": false,
- "supportsInventory": false
- },
"store_types": [
{
"Name": "iDRAC",
@@ -42,7 +27,30 @@
"Enrollment": false,
"Remove": false
},
- "Properties": [],
+ "Properties": [
+ {
+ "Name": "ServerUsername",
+ "DisplayName": "Server Username",
+ "Type": "Secret",
+ "DependsOn": "",
+ "DefaultValue": "",
+ "Required": true,
+ "IsPAMEligible": true,
+ "Description": "The user ID (or, if using a PAM provider, the key pointing to the user ID) to log into the iDRAC instance being managed."
+ },
+ {
+ "Name": "ServerPassword",
+ "DisplayName": "Server Password",
+ "Type": "Secret",
+ "DependsOn": "",
+ "DefaultValue": "",
+ "Required": true,
+ "IsPAMEligible": true,
+ "Description": "The password (or, if using a PAM provider, the key pointing to the password) for the user ID above."
+ }
+ ],
+ "ClientMachineDescription": "The IP address of the iDRAC instance being managed.",
+ "StorePathDescription": "Enter the full path where the Racadm executable is installed on the orchestrator server. See [Requirements & Prerequisites](#requirements-&-prerequisites) above for more details.",
"EntryParameters": [],
"PasswordOptions": {
"EntrySupported": false,
diff --git a/readme-src/readme-pam-support.md b/readme-src/readme-pam-support.md
deleted file mode 100644
index 02164cf..0000000
--- a/readme-src/readme-pam-support.md
+++ /dev/null
@@ -1,5 +0,0 @@
-|Name|Description|
-|----|-----------|
-|ServerUsername|The user id that will be used to authenticate into the Dell Remote Access Controller|
-|ServerPassword|The password that will be used to authenticate into the Dell Remote Access Controller|
-
diff --git a/readme_source.md b/readme_source.md
deleted file mode 100644
index f9258b6..0000000
--- a/readme_source.md
+++ /dev/null
@@ -1,106 +0,0 @@
-
-## Overview
-
-The Integrated Dell Remote Access Controller (iDRAC) Orchestrator Extension supports the following use cases:
-
-- Inventorying the iDRAC instance's server certificate and importing it into Keyfactor Command for management
-- Adding or Replacing an existing or newly enrolled certificate and private key to an existing iDRAC instance. To replace an existing server certificate, the Ovewrite flag in Keyfactor Command must be selected.
-
-Use cases NOT supported by the iDRAC Orchestrator Extension:
-
-- Removing a server certificate from an iDRAC instance.
-- Inventorying or Managing any other certificate type on an iDRAC intance.
-
-Special Notes:
-* When adding or replacing the server certificate, there will be a few minute delay as the iDRAC instance will restart. As a result, it may take a few minutes before the new certificate is reflected in subsequent Inventory jobs.
-* When replacing an existing server certificate, the Overwrite checkbox must be selected/checked. When this checkbox is selected, Keyfactor Command may require you to enter an alias. This alias is not used by the orchestrator extension, so just enter any value.
-
-
-## Versioning
-
-The version number of a the Integrated Dell Remote Access Controller (iDRAC) Orchestrator Extension can be verified by right clicking on the DellIDRACOrchestrator.dll file in the Extensions/DellIdrac installation folder, selecting Properties, and then clicking on the Details tab.
-
-
-## Installation Prerequisites
-
-1. The Orchestrator must run on a Windows Server machine with the [Racadm CLI utility](https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=8gmf6) installed, configured to reach the target iDRAC instance. The Orchestrator must have read and write access to the folder where racadm.exe is installed.
-2. A user id must be set up in iDRAC with minimum privileges of "Configure". This will be used by the Racadm utility to manage the store.
-
-
-## iDRAC Orchestrator Extension Installation
-
-1. Stop the Keyfactor Universal Orchestrator Service.
-2. In the Keyfactor Orchestrator installation folder (by convention usually C:\Program Files\Keyfactor\Keyfactor Orchestrator), find the "extensions" folder. Underneath that, create a new folder named DellIdrac or another name of your choosing.
-3. Download the latest version of the iDRAC Orchestrator Extension from [GitHub](https://github.com/Keyfactor/dell-idrac-orchestrator).
-4. Copy the contents of the download installation zip file into the folder created in step 2.
-5. Start the Keyfactor Universal Orchestrator Service.
-6. In Keyfactor Command, under Orchestrators => Management, approve the orchestrator you just installed the extension on.
-
-
-## iDRAC Orchestrator Extension Configuration
-
-### Create an iDRAC Certificate Store Type
-
-In Keyfactor Command, create a new certificate store type by navigating to Settings (the "gear" icon in the top right) => Certificate Store Types, and clicking ADD. Then enter the following information:
-
-Custom Fields Tab
+* **Using kfutil** + +Create Certificate Stores with kfutil
+ + 1. **Generate a CSV template for the iDRAC certificate store** -Not Used + ```shell + kfutil stores import generate-template --store-type-name iDRAC --outpath iDRAC.csv + ``` + 2. **Populate the generated CSV file** -
-
+ Entry Parameters Tab
-Not Used + -Attributes eligible for retrieval by a PAM Provider on the Universal Orchestrator
+ 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_. + | Attribute | Description | + | --------- | ----------- | + | ServerUsername | The user ID (or, if using a PAM provider, the key pointing to the user ID) to log into the iDRAC instance being managed. | + | ServerPassword | The password (or, if using a PAM provider, the key pointing to the password) for the user ID above. | -### Create an iDRAC Certificate Store -Navigate to Certificate Locations =\> Certificate Stores within Keyfactor Command to add the store. Below are the values that should be entered: + > 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. +
-
-
-Basic Tab
- -- **Name** – Required. The descriptive display name of the new Certificate Store Type. Suggested => iDRAC -- **Short Name** – Required. This value ***must be*** iDRAC. -- **Custom Capability** - Leave unchecked -- **Supported Job Types** – Select Inventory and Add. -- **General Settings** - Select Needs Server. Select Blueprint Allowed if you plan to use blueprinting. Leave Uses PowerShell unchecked. -- **Password Settings** - Leave both options unchecked - -
-
-
-Advanced Tab
- -- **Store Path Type** - Select Freeform -- **Supports Custom Alias** - Forbidden -- **Private Key Handling** - Required -- **PFX Password Style** - Default - -
-
-
-Custom Fields Tab
- -Not Used - -
-
-
-
-### Create an iDRAC Certificate Store
-
-Navigate to Certificate Locations =\> Certificate Stores within Keyfactor Command to add the store. Below are the values that should be entered:
-
-- **Category** – Required. Select the Name you entered when creating the Certificate Store Type. Suggested value was iDRAC.
-
-- **Container** – Optional. Select a container if utilized.
-
-- **Client Machine** – Required. The IP address of the iDRAC instance being managed.
-
-- **Store Path** – Required. Enter the full path where the Racadm executable is installed on the Orchestrator server. See [Installation Prerequisites](#installation-prerequisites) for more details.
-
-- **Orchestrator** – Required. Select the orchestrator you wish to use to manage this store
-
-- **Server Username/Password** - Required. The credentials used to log into the iDRAC instance being managed. These values for server login can be either:
-
- - UserId/Password
- - PAM provider information used to look up the UserId/Password credentials
-
- Please make sure the user id entered has "Configure" privileges on the iDRAC instance.
-
-- **Use SSL** - N/A. This value is not referenced in the iDRAC Orchestrator Extension.
-
-- **Inventory Schedule** – Set a schedule for running Inventory jobs or "none", if you choose not to schedule Inventory at this time.
\ No newline at end of file
diff --git a/store-type.json b/store-type.json
deleted file mode 100644
index 3cf8381..0000000
--- a/store-type.json
+++ /dev/null
@@ -1,62 +0,0 @@
-[
- {
- "Name": "Dell IDRAC",
- "ShortName": "IDRAC",
- "Capability": "IDRAC",
- "StoreType": 106,
- "ImportType": 106,
- "LocalStore": false,
- "SupportedOperations": {
- "Add": true,
- "Create": false,
- "Discovery": false,
- "Enrollment": false,
- "Remove": false
- },
- "Properties": [
- {
- "StoreTypeId": 106,
- "Name": "ServerUsername",
- "DisplayName": "Server Username",
- "Type": "Secret",
- "DependsOn": null,
- "DefaultValue": null,
- "Required": false
- },
- {
- "StoreTypeId": 106,
- "Name": "ServerPassword",
- "DisplayName": "Server Password",
- "Type": "Secret",
- "DependsOn": null,
- "DefaultValue": null,
- "Required": false
- },
- {
- "StoreTypeId": 106,
- "Name": "ServerUseSsl",
- "DisplayName": "Use SSL",
- "Type": "Bool",
- "DependsOn": null,
- "DefaultValue": "true",
- "Required": true
- }
- ],
- "EntryParameters": [],
- "PasswordOptions": {
- "EntrySupported": false,
- "StoreRequired": false,
- "Style": "Default"
- },
- "PrivateKeyAllowed": "Required",
- "JobProperties": [],
- "ServerRequired": true,
- "PowerShell": false,
- "BlueprintAllowed": false,
- "CustomAliasAllowed": "Forbidden",
- "ServerRegistration": 8,
- "InventoryEndpoint": "/AnyInventory/Update",
- "InventoryJobType": "baa226b7-99d6-4944-85c7-3f1ad6f75a5d",
- "ManagementJobType": "c414b46c-d57b-41e3-816f-3a1473f682b4"
- }
-]
\ No newline at end of file