{"id":25190082,"url":"https://github.com/keyfactor/ibm-datapower-orchestrator","last_synced_at":"2026-05-01T21:05:32.932Z","repository":{"id":163203213,"uuid":"499318579","full_name":"Keyfactor/ibm-datapower-orchestrator","owner":"Keyfactor","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. For example default\\pubcert","archived":false,"fork":false,"pushed_at":"2026-05-01T13:39:35.000Z","size":360,"stargazers_count":0,"open_issues_count":2,"forks_count":0,"subscribers_count":5,"default_branch":"main","last_synced_at":"2026-05-01T15:28:37.175Z","etag":null,"topics":["keyfactor-integration","keyfactor-universal-orchestrator"],"latest_commit_sha":null,"homepage":"","language":"C#","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/Keyfactor.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2022-06-02T23:17:35.000Z","updated_at":"2026-01-15T00:40:06.000Z","dependencies_parsed_at":null,"dependency_job_id":"9107b0fe-d98f-410a-8f0f-99fad98b894d","html_url":"https://github.com/Keyfactor/ibm-datapower-orchestrator","commit_stats":null,"previous_names":[],"tags_count":45,"template":false,"template_full_name":null,"purl":"pkg:github/Keyfactor/ibm-datapower-orchestrator","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Keyfactor%2Fibm-datapower-orchestrator","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Keyfactor%2Fibm-datapower-orchestrator/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Keyfactor%2Fibm-datapower-orchestrator/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Keyfactor%2Fibm-datapower-orchestrator/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/Keyfactor","download_url":"https://codeload.github.com/Keyfactor/ibm-datapower-orchestrator/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Keyfactor%2Fibm-datapower-orchestrator/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":32512703,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-04-30T13:12:12.517Z","status":"online","status_checked_at":"2026-05-01T02:00:05.856Z","response_time":64,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["keyfactor-integration","keyfactor-universal-orchestrator"],"created_at":"2025-02-09T21:18:53.558Z","updated_at":"2026-05-01T21:05:32.917Z","avatar_url":"https://github.com/Keyfactor.png","language":"C#","funding_links":[],"categories":[],"sub_categories":[],"readme":"\u003ch1 align=\"center\" style=\"border-bottom: none\"\u003e\n    DataPower Universal Orchestrator Extension\n\u003c/h1\u003e\n\n\u003cp align=\"center\"\u003e\n  \u003c!-- Badges --\u003e\n\u003cimg src=\"https://img.shields.io/badge/integration_status-production-3D1973?style=flat-square\" alt=\"Integration Status: production\" /\u003e\n\u003ca href=\"https://github.com/Keyfactor/ibm-datapower-orchestrator/releases\"\u003e\u003cimg src=\"https://img.shields.io/github/v/release/Keyfactor/ibm-datapower-orchestrator?style=flat-square\" alt=\"Release\" /\u003e\u003c/a\u003e\n\u003cimg src=\"https://img.shields.io/github/issues/Keyfactor/ibm-datapower-orchestrator?style=flat-square\" alt=\"Issues\" /\u003e\n\u003cimg src=\"https://img.shields.io/github/downloads/Keyfactor/ibm-datapower-orchestrator/total?style=flat-square\u0026label=downloads\u0026color=28B905\" alt=\"GitHub Downloads (all assets, all releases)\" /\u003e\n\u003c/p\u003e\n\n\u003cp align=\"center\"\u003e\n  \u003c!-- TOC --\u003e\n  \u003ca href=\"#support\"\u003e\n    \u003cb\u003eSupport\u003c/b\u003e\n  \u003c/a\u003e\n  ·\n  \u003ca href=\"#installation\"\u003e\n    \u003cb\u003eInstallation\u003c/b\u003e\n  \u003c/a\u003e\n  ·\n  \u003ca href=\"#license\"\u003e\n    \u003cb\u003eLicense\u003c/b\u003e\n  \u003c/a\u003e\n  ·\n  \u003ca href=\"https://github.com/orgs/Keyfactor/repositories?q=orchestrator\"\u003e\n    \u003cb\u003eRelated Integrations\u003c/b\u003e\n  \u003c/a\u003e\n\u003c/p\u003e\n\n## Overview\n\nThe 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. \n\n* DataPower\n\n\n\n## Compatibility\n\nThis integration is compatible with Keyfactor Universal Orchestrator version 10.4 and later.\n\n## Support\nThe DataPower Universal Orchestrator extension is supported by Keyfactor. If you require support for any issues or have feature request, please open a support ticket by either contacting your Keyfactor representative or via the Keyfactor Support Portal at https://support.keyfactor.com.\n\n\u003e If you want to contribute bug fixes or additional enhancements, use the **[Pull requests](../../pulls)** tab.\n\n## Requirements \u0026 Prerequisites\n\nBefore installing the DataPower 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.\n\n\nThe 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.  For example default\\pubcert\n\n\n## DataPower Certificate Store Type\n\nTo use the DataPower Universal Orchestrator extension, you **must** create the DataPower Certificate Store Type. This only needs to happen _once_ per Keyfactor Command instance.\n\n\n\n\n\n\n\n\n#### Supported Operations\n\n| Operation    | Is Supported                                                                                                           |\n|--------------|------------------------------------------------------------------------------------------------------------------------|\n| Add          | ✅ Checked        |\n| Remove       | 🔲 Unchecked     |\n| Discovery    | 🔲 Unchecked  |\n| Reenrollment | 🔲 Unchecked |\n| Create       | 🔲 Unchecked     |\n\n#### Store Type Creation\n\n##### Using kfutil:\n`kfutil` is a custom CLI for the Keyfactor Command API and can be used to create certificate store types.\nFor more information on [kfutil](https://github.com/Keyfactor/kfutil) check out the [docs](https://github.com/Keyfactor/kfutil?tab=readme-ov-file#quickstart)\n   \u003cdetails\u003e\u003csummary\u003eClick to expand DataPower kfutil details\u003c/summary\u003e\n\n   ##### Using online definition from GitHub:\n   This will reach out to GitHub and pull the latest store-type definition\n   ```shell\n   # IBM Data Power\n   kfutil store-types create DataPower\n   ```\n\n   ##### Offline creation using integration-manifest file:\n   If required, it is possible to create store types from the [integration-manifest.json](./integration-manifest.json) included in this repo.\n   You would first download the [integration-manifest.json](./integration-manifest.json) and then run the following command\n   in your offline environment.\n   ```shell\n   kfutil store-types create --from-file integration-manifest.json\n   ```\n   \u003c/details\u003e\n\n\n#### Manual Creation\nBelow are instructions on how to create the DataPower store type manually in\nthe Keyfactor Command Portal\n   \u003cdetails\u003e\u003csummary\u003eClick to expand manual DataPower details\u003c/summary\u003e\n\n   Create a store type called `DataPower` with the attributes in the tables below:\n\n   ##### Basic Tab\n   | Attribute | Value | Description |\n   | --------- | ----- | ----- |\n   | Name | IBM Data Power | Display name for the store type (may be customized) |\n   | Short Name | DataPower | Short display name for the store type |\n   | Capability | DataPower | Store type name orchestrator will register with. Check the box to allow entry of value |\n   | Supports Add | ✅ Checked | Check the box. Indicates that the Store Type supports Management Add |\n   | Supports Remove | 🔲 Unchecked |  Indicates that the Store Type supports Management Remove |\n   | Supports Discovery | 🔲 Unchecked |  Indicates that the Store Type supports Discovery |\n   | Supports Reenrollment | 🔲 Unchecked |  Indicates that the Store Type supports Reenrollment |\n   | Supports Create | 🔲 Unchecked |  Indicates that the Store Type supports store creation |\n   | Needs Server | ✅ Checked | Determines if a target server name is required when creating store |\n   | Blueprint Allowed | 🔲 Unchecked | Determines if store type may be included in an Orchestrator blueprint |\n   | Uses PowerShell | 🔲 Unchecked | Determines if underlying implementation is PowerShell |\n   | Requires Store Password | 🔲 Unchecked | Enables users to optionally specify a store password when defining a Certificate Store. |\n   | Supports Entry Password | 🔲 Unchecked | Determines if an individual entry within a store can have a password. |\n\n   The Basic tab should look like this:\n\n   ![DataPower Basic Tab](docsource/images/DataPower-basic-store-type-dialog.png)\n\n   ##### Advanced Tab\n   | Attribute | Value | Description |\n   | --------- | ----- | ----- |\n   | Supports Custom Alias | Required | Determines if an individual entry within a store can have a custom Alias. |\n   | Private Key Handling | Optional | 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. |\n   | 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.) |\n\n   The Advanced tab should look like this:\n\n   ![DataPower Advanced Tab](docsource/images/DataPower-advanced-store-type-dialog.png)\n\n   \u003e For Keyfactor **Command versions 24.4 and later**, a Certificate Format dropdown is available with PFX and PEM options. Ensure that **PFX** is selected, as this determines the format of new and renewed certificates sent to the Orchestrator during a Management job. Currently, all Keyfactor-supported Orchestrator extensions support only PFX.\n\n   ##### Custom Fields Tab\n   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:\n\n   | Name | Display Name | Description | Type | Default Value/Options | Required |\n   | ---- | ------------ | ---- | --------------------- | -------- | ----------- |\n   | ServerUsername | Server Username | Api UserName for DataPower. (or valid PAM key if the username is stored in a KF Command configured PAM integration). | Secret |  | 🔲 Unchecked |\n   | ServerPassword | Server Password | A password for DataPower API access.  Used for inventory.(or valid PAM key if the password is stored in a KF Command configured PAM integration). | Secret |  | 🔲 Unchecked |\n   | ServerUseSsl | Use SSL | Should be true, http is not supported. | Bool | true | ✅ Checked |\n   | InventoryBlackList | Inventory Black List | Comma seperated list of alias values you do not want to inventory from DataPower. | String |  | 🔲 Unchecked |\n   | Protocol | Protocol Name | Comma seperated list of alias values you do not want to inventory from DataPower. | String | https | ✅ Checked |\n   | PublicCertStoreName | Public Cert Store Name | This probably will remain pubcert unless someone changed the default name in DataPower. | String | pubcert | ✅ Checked |\n   | InventoryPageSize | Inventory Page Size | This determines the page size during the inventory calls. (100 should be fine). | String | 100 | ✅ Checked |\n\n   The Custom Fields tab should look like this:\n\n   ![DataPower Custom Fields Tab](docsource/images/DataPower-custom-fields-store-type-dialog.png)\n\n\n   ###### Server Username\n   Api UserName for DataPower. (or valid PAM key if the username is stored in a KF Command configured PAM integration).\n\n\n   \u003e [!IMPORTANT]\n   \u003e This field is created by the `Needs Server` on the Basic tab, do not create this field manually.\n\n\n\n\n   ###### Server Password\n   A password for DataPower API access.  Used for inventory.(or valid PAM key if the password is stored in a KF Command configured PAM integration).\n\n\n   \u003e [!IMPORTANT]\n   \u003e This field is created by the `Needs Server` on the Basic tab, do not create this field manually.\n\n\n\n\n   ###### Use SSL\n   Should be true, http is not supported.\n\n   ![DataPower Custom Field - ServerUseSsl](docsource/images/DataPower-custom-field-ServerUseSsl-dialog.png)\n\n\n\n   ###### Inventory Black List\n   Comma seperated list of alias values you do not want to inventory from DataPower.\n\n   ![DataPower Custom Field - InventoryBlackList](docsource/images/DataPower-custom-field-InventoryBlackList-dialog.png)\n\n\n\n   ###### Protocol Name\n   Comma seperated list of alias values you do not want to inventory from DataPower.\n\n   ![DataPower Custom Field - Protocol](docsource/images/DataPower-custom-field-Protocol-dialog.png)\n\n\n\n   ###### Public Cert Store Name\n   This probably will remain pubcert unless someone changed the default name in DataPower.\n\n   ![DataPower Custom Field - PublicCertStoreName](docsource/images/DataPower-custom-field-PublicCertStoreName-dialog.png)\n\n\n\n   ###### Inventory Page Size\n   This determines the page size during the inventory calls. (100 should be fine).\n\n   ![DataPower Custom Field - InventoryPageSize](docsource/images/DataPower-custom-field-InventoryPageSize-dialog.png)\n\n\n\n\n\n   \u003c/details\u003e\n\n## Installation\n\n1. **Download the latest DataPower Universal Orchestrator extension from GitHub.**\n\n    Navigate to the [DataPower Universal Orchestrator extension GitHub version page](https://github.com/Keyfactor/ibm-datapower-orchestrator/releases/latest). Refer to the compatibility matrix below to determine the asset should be downloaded. Then, click the corresponding asset to download the zip archive.\n\n   | Universal Orchestrator Version | Latest .NET version installed on the Universal Orchestrator server | `rollForward` condition in `Orchestrator.runtimeconfig.json` | `ibm-datapower-orchestrator` .NET version to download |\n   | --------- | ----------- | ----------- | ----------- |\n   | Older than `11.0.0` | | | `net6.0` |\n   | Between `11.0.0` and `11.5.1` (inclusive) | `net6.0` | | `net6.0` |\n   | Between `11.0.0` and `11.5.1` (inclusive) | `net8.0` | `Disable` | `net6.0` || Between `11.0.0` and `11.5.1` (inclusive) | `net8.0` | `LatestMajor` | `net8.0` |\n   | `11.6` _and_ newer | `net8.0` | | `net8.0` | \n\n    Unzip the archive containing extension assemblies to a known location.\n\n    \u003e **Note** If you don't see an asset with a corresponding .NET version, you should always assume that it was compiled for `net6.0`.\n\n2. **Locate the Universal Orchestrator extensions directory.**\n\n    * **Default on Windows** - `C:\\Program Files\\Keyfactor\\Keyfactor Orchestrator\\extensions`\n    * **Default on Linux** - `/opt/keyfactor/orchestrator/extensions`\n\n3. **Create a new directory for the DataPower Universal Orchestrator extension inside the extensions directory.**\n\n    Create a new directory called `ibm-datapower-orchestrator`.\n    \u003e The directory name does not need to match any names used elsewhere; it just has to be unique within the extensions directory.\n\n4. **Copy the contents of the downloaded and unzipped assemblies from __step 2__ to the `ibm-datapower-orchestrator` directory.**\n\n5. **Restart the Universal Orchestrator service.**\n\n    Refer to [Starting/Restarting the Universal Orchestrator service](https://software.keyfactor.com/Core-OnPrem/Current/Content/InstallingAgents/NetCoreOrchestrator/StarttheService.htm).\n\n\n6. **(optional) PAM Integration**\n\n    The DataPower 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.\n\n    To configure a PAM provider, [reference the Keyfactor Integration Catalog](https://keyfactor.github.io/integrations-catalog/content/pam) to select an extension and follow the associated instructions to install it on the Universal Orchestrator (remote).\n\n\n\u003e The above installation steps can be supplemented by the [official Command documentation](https://software.keyfactor.com/Core-OnPrem/Current/Content/InstallingAgents/NetCoreOrchestrator/CustomExtensions.htm?Highlight=extensions).\n\n\n\n## Defining Certificate Stores\n\n\n\n### Store Creation\n\n#### Manually with the Command UI\n\n\u003cdetails\u003e\u003csummary\u003eClick to expand details\u003c/summary\u003e\n\n1. **Navigate to the _Certificate Stores_ page in Keyfactor Command.**\n\n    Log into Keyfactor Command, toggle the _Locations_ dropdown, and click _Certificate Stores_.\n\n2. **Add a Certificate Store.**\n\n    Click the Add button to add a new Certificate Store. Use the table below to populate the **Attributes** in the **Add** form.\n\n   | Attribute | Description                                             |\n   | --------- |---------------------------------------------------------|\n   | Category | Select \"IBM Data Power\" or the customized certificate store name from the previous step. |\n   | Container | Optional container to associate certificate store with. |\n   | Client Machine | The Client Machine field should contain the IP or Domain name and Port Needed for REST API Access.  For SSH Access, Port 22 will be used. |\n   | Store Path | The Store Path field should always be / unless we later determine there are alternate locations needed. |\n   | Orchestrator | Select an approved orchestrator capable of managing `DataPower` certificates. Specifically, one with the `DataPower` capability. |\n   | ServerUsername | Api UserName for DataPower. (or valid PAM key if the username is stored in a KF Command configured PAM integration). |\n   | ServerPassword | A password for DataPower API access.  Used for inventory.(or valid PAM key if the password is stored in a KF Command configured PAM integration). |\n   | ServerUseSsl | Should be true, http is not supported. |\n   | InventoryBlackList | Comma seperated list of alias values you do not want to inventory from DataPower. |\n   | Protocol | Comma seperated list of alias values you do not want to inventory from DataPower. |\n   | PublicCertStoreName | This probably will remain pubcert unless someone changed the default name in DataPower. |\n   | InventoryPageSize | This determines the page size during the inventory calls. (100 should be fine). |\n\n\u003c/details\u003e\n\n\n\n#### Using kfutil CLI\n\n\u003cdetails\u003e\u003csummary\u003eClick to expand details\u003c/summary\u003e\n\n1. **Generate a CSV template for the DataPower certificate store**\n\n    ```shell\n    kfutil stores import generate-template --store-type-name DataPower --outpath DataPower.csv\n    ```\n2. **Populate the generated CSV file**\n\n    Open the CSV file, and reference the table below to populate parameters for each **Attribute**.\n\n   | Attribute | Description |\n   | --------- | ----------- |\n   | Category | Select \"IBM Data Power\" or the customized certificate store name from the previous step. |\n   | Container | Optional container to associate certificate store with. |\n   | Client Machine | The Client Machine field should contain the IP or Domain name and Port Needed for REST API Access.  For SSH Access, Port 22 will be used. |\n   | Store Path | The Store Path field should always be / unless we later determine there are alternate locations needed. |\n   | Orchestrator | Select an approved orchestrator capable of managing `DataPower` certificates. Specifically, one with the `DataPower` capability. |\n   | Properties.ServerUsername | Api UserName for DataPower. (or valid PAM key if the username is stored in a KF Command configured PAM integration). |\n   | Properties.ServerPassword | A password for DataPower API access.  Used for inventory.(or valid PAM key if the password is stored in a KF Command configured PAM integration). |\n   | Properties.ServerUseSsl | Should be true, http is not supported. |\n   | Properties.InventoryBlackList | Comma seperated list of alias values you do not want to inventory from DataPower. |\n   | Properties.Protocol | Comma seperated list of alias values you do not want to inventory from DataPower. |\n   | Properties.PublicCertStoreName | This probably will remain pubcert unless someone changed the default name in DataPower. |\n   | Properties.InventoryPageSize | This determines the page size during the inventory calls. (100 should be fine). |\n\n3. **Import the CSV file to create the certificate stores**\n\n    ```shell\n    kfutil stores import csv --store-type-name DataPower --file DataPower.csv\n    ```\n\n\u003c/details\u003e\n\n\n#### PAM Provider Eligible Fields\n\u003cdetails\u003e\u003csummary\u003eAttributes eligible for retrieval by a PAM Provider on the Universal Orchestrator\u003c/summary\u003e\n\nIf 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_.\n\n   | Attribute | Description |\n   | --------- | ----------- |\n   | ServerUsername | Api UserName for DataPower. (or valid PAM key if the username is stored in a KF Command configured PAM integration). |\n   | ServerPassword | A password for DataPower API access.  Used for inventory.(or valid PAM key if the password is stored in a KF Command configured PAM integration). |\n\nPlease 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.\n\u003e 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.\n\n\u003c/details\u003e\n\n\n\u003e The content in this section can be supplemented by the [official Command documentation](https://software.keyfactor.com/Core-OnPrem/Current/Content/ReferenceGuide/Certificate%20Stores.htm?Highlight=certificate%20store).\n\n\n\n\n## Test Cases\n\n*** \n\n#### INVENTORY TEST CASES\nCase Number|Case Name|Case Description|Expected Results|Passed\n------------|---------|----------------|--------------|----------\n1|Pubcert Inventory No Black List Default Domain|Should Inventory Everything in the DataPower pubcert directory on the Default Domain|Keyfactor Inventory Matches pubcert default domain inventory|True\n1a|Pubcert Inventory No Black List Default Domain using PAM Credentials|Should Inventory Everything in the DataPower pubcert directory on the Default Domain using credentials stored in a PAM Provider|Keyfactor Inventory Matches pubcert default domain inventory|True\n1b|Pubcert Inventory With Black List Default Domain|Should Inventory Everything in the DataPower pubcert directory on the Default Domain Outside of Black List Items ex: Test.pem,Test2.pem|Keyfactor Inventory Matches pubcert default domain inventory outside of Black List Items|True\n2|Pubcert Inventory No Black List *testdomain\\pubcert* path|Should Inventory Everything in the DataPower pubcert directory on the *testdomain\\pubcert* path|Keyfactor Inventory Matches pubcert default domain inventory|True\n2a|Pubcert Inventory With Black List *testdomain\\pubcert* path|Should Inventory Everything in the DataPower pubcert directory on the *testdomain\\pubcert* path Outside of Black List Items ex: Cert1.pem,Cert2.pem|Keyfactor Inventory Matches pubcert default domain inventory outside of Black List Items|True\n3|Private Key Cert Inventory No Black List Default Domain|Should Inventory Everything in the DataPower cert directory on the Default Domain|Keyfactor Inventory Matches pubcert default domain inventory|True\n3a|Private Key Cert Inventory No Black List Default Domain with Credentials Stored in PAM Provider|Should Inventory Everything in the DataPower cert directory on the Default Domain with Credentials Stored in PAM Provider|Keyfactor Inventory Matches pubcert default domain inventory|True\n3b|Private Key Cert Inventory With Black List Default Domain|Should Inventory Everything in the DataPower cert directory on the Default Domain Oustide of Black List Items ex: Test.pem,Test2.pem|Keyfactor Inventory Matches cert default domain inventory outside of Black List Items|True\n4|Private Key Cert Inventory No Black List *testdomain\\cert* path|Should Inventory Everything in the DataPower cert directory on the  *testdomain\\cert* path|Keyfactor Inventory Matches *testdomain\\cert* path| inventory|True\n4a|Private Key Cert Inventory With Black List *testdomain\\cert* path||Should Inventory Everything in the DataPower cert directory on the  *testdomain\\cert* path|Keyfactor Inventory Matches *testdomain\\cert* path Oustide of Black List Items ex: Test,Test2|Keyfactor Inventory Matches everything in *testdomain\\cert* path outside of Black List Items\n\n***\n\n#### ADD/REMOVE TEST CASES\nCase Number|Case Name|Case Description|Overwrite Flag|Alias Name|Expected Results|Passed\n------------|---------|----------------|--------------|----------|----------------|--------------\n1|Pubcert Add with Alias Default Domain|Will create new Cert, Key and Pem/crt entry|False|cryptoobjs|Crypto Key Created, Crypto Cert Created, Pem/Crt created|True\n1a|Pubcert Overwrite with Alias Default Domain|Will Replaced Cert, Key and Pem/crt entry|true|cryptoobjs|Crypto Key Replaced, Crypto Cert Replaced, Pem/Crt Replaced|True\n1b|Pubcert Add without Alias Default Domain|Will create new Cert, Key and Pem/crt entry with GUID as name|False|cryptoobjs|Crypto Key Created, Crypto Cert Created, Pem/Crt created with GUID as name|True\n2|Private Key Add with Alias Default Domain|Will create new Cert, Key and Pem/crt entry|False|cryptoobjs|Crypto Key Created, Crypto Cert Created, Pem/Crt created|True\n2a|Private Key Overwrite with Alias Default Domain|Will Replaced Cert, Key and Pem/crt entry|true|cryptoobjs|Crypto Key Replaced, Crypto Cert Replaced, Pem/Crt Replaced|True\n2b|Private Key Add without Alias Default Domain|Will create new Cert, Key and Pem/crt entry with GUID as name|False|cryptoobjs|Crypto Key Created, Crypto Cert Created, Pem/Crt created with GUID as name|True\n2c|Private Key Cert Add with Alias *testdomain\\cert* path|Will create new Cert, Key and Pem/crt entry in *testdomain\\cert* path|False|cryptoobjs|Crypto Key Created, Crypto Cert Created, Pem/Crt created in *testdomain\\pubcert* path|True\n2d|Private Key Cert Add with Alias *testdomain\\cert* path|Will create new Cert, Key and Pem/crt entry in *testdomain\\cert* path with PAM Credentials|False|cryptoobjs|Crypto Key Created, Crypto Cert Created, Pem/Crt created in *testdomain\\pubcert* path gettting credentials from a PAM Provider|True\n3a|Private Key Cert Overwrite with Alias *testdomain\\cert* path|Will Replaced Cert, Key and Pem/crt entry in *testdomain\\cert* path|true|cryptoobjs|Crypto Key Replaced, Crypto Cert Replaced, Pem/Crt Replaced in *testdomain\\pubcert* path|True\n3b|Private Key Cert Add without Alias *testdomain\\cert* path|Will create new Cert, Key and Pem/crt entry with GUID as name in *testdomain\\cert* path|False|cryptoobjs|Crypto Key Created, Crypto Cert Created, Pem/Crt created with GUID as name in *testdomain\\cert* path|True\n4|Remove Private Key and Cert From Default Domain|Remove Private Key and Cert From Default Domain|False|cryptoobjs|Crypto Certificate, Crypto Key and Pem/Crt are removed from Data Power|True\n4a|Remove Private Key and Cert From *testdomain\\cert* path|Remove Private Key and Cert From *testdomain\\cert* path|False|cryptoobjs|Crypto Certificate, Crypto Key and Pem/Crt are removed from Data Power *testdomain\\cert* path|True\n4b|Remove PubCert|Remove PubCert|False|cryptoobjs|Error Occurs, cannot remove Public Certs|True\n4c|Remove Private Key and Cert From *testdomain\\cert* path with PAM Credentials|Remove Private Key and Cert From *testdomain\\cert* path using credentials stored in a PAM Provider|False|cryptoobjs|Crypto Certificate, Crypto Key and Pem/Crt are removed from Data Power *testdomain\\cert* path|True\n\n***\n\n\n## License\n\nApache License 2.0, see [LICENSE](LICENSE).\n\n## Related Integrations\n\nSee all [Keyfactor Universal Orchestrator extensions](https://github.com/orgs/Keyfactor/repositories?q=orchestrator).","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fkeyfactor%2Fibm-datapower-orchestrator","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fkeyfactor%2Fibm-datapower-orchestrator","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fkeyfactor%2Fibm-datapower-orchestrator/lists"}