diff --git a/.github/workflows/keyfactor-configure-repository-workflow.yml b/.github/workflows/keyfactor-configure-repository-workflow.yml
deleted file mode 100644
index daa0f96..0000000
--- a/.github/workflows/keyfactor-configure-repository-workflow.yml
+++ /dev/null
@@ -1,19 +0,0 @@
-name: Configure Repository Workflow
-on: [workflow_dispatch]
-
-jobs:
- call-update-topic:
- uses: Keyfactor/actions/.github/workflows/kf-update-topics.yml@main
- secrets:
- token: ${{ secrets.GH_REPO_CONFIG }}
-
- call-update-description:
- uses: Keyfactor/actions/.github/workflows/kf-update-description.yml@main
- secrets:
- token: ${{ secrets.GH_REPO_CONFIG }}
-
- call-update-teams:
- uses: Keyfactor/actions/.github/workflows/kf-update-teams.yml@main
- secrets:
- token: ${{ secrets.GH_REPO_CONFIG }}
-
diff --git a/.github/workflows/keyfactor-merge-store-types.yml b/.github/workflows/keyfactor-merge-store-types.yml
deleted file mode 100644
index e8b1e82..0000000
--- a/.github/workflows/keyfactor-merge-store-types.yml
+++ /dev/null
@@ -1,27 +0,0 @@
-name: Keyfactor Merge Cert Store Types
-on: [workflow_dispatch]
-
-jobs:
- get-manifest-properties:
- runs-on: windows-latest
- outputs:
- update_catalog: ${{ steps.read-json.outputs.update_catalog }}
- integration_type: ${{ steps.read-json.outputs.integration_type }}
- steps:
- - uses: actions/checkout@v3
- - name: Store json
- id: read-json
- shell: pwsh
- run: |
- $json = Get-Content integration-manifest.json | ConvertFrom-Json
- $myvar = $json.update_catalog
- echo "update_catalog=$myvar" | Out-File -FilePath $Env:GITHUB_OUTPUT -Encoding utf8 -Append
- $myvar = $json.integration_type
- echo "integration_type=$myvar" | Out-File -FilePath $Env:GITHUB_OUTPUT -Encoding utf8 -Append
-
- call-update-store-types-workflow:
- needs: get-manifest-properties
- if: needs.get-manifest-properties.outputs.integration_type == 'orchestrator' && (github.event_name == 'push' || github.event_name == 'workflow_dispatch')
- uses: Keyfactor/actions/.github/workflows/update-store-types.yml@main
- secrets:
- token: ${{ secrets.UPDATE_STORE_TYPES }}
diff --git a/.github/workflows/keyfactor-starter-workflow.yml b/.github/workflows/keyfactor-starter-workflow.yml
index eb977c6..61ea7a0 100644
--- a/.github/workflows/keyfactor-starter-workflow.yml
+++ b/.github/workflows/keyfactor-starter-workflow.yml
@@ -1,33 +1,20 @@
-name: Starter Workflow
-on: [workflow_dispatch, push, pull_request]
+name: Keyfactor Bootstrap Workflow
-jobs:
- call-create-github-release-workflow:
- uses: Keyfactor/actions/.github/workflows/github-release.yml@main
-
- call-assign-from-json-workflow:
- uses: Keyfactor/actions/.github/workflows/assign-env-from-json.yml@main
-
- call-dotnet-build-and-release-workflow:
- needs: [call-create-github-release-workflow, call-assign-from-json-workflow]
- uses: Keyfactor/actions/.github/workflows/dotnet-build-and-release.yml@main
- with:
- release_version: ${{ needs.call-create-github-release-workflow.outputs.release_version }}
- release_url: ${{ needs.call-create-github-release-workflow.outputs.release_url }}
- release_dir: ${{ needs.call-assign-from-json-workflow.outputs.release_dir }}
+on:
+ workflow_dispatch:
+ pull_request:
+ types: [opened, closed, synchronize, edited, reopened]
+ push:
+ create:
+ branches:
+ - 'release-*.*'
- secrets:
- token: ${{ secrets.PRIVATE_PACKAGE_ACCESS }}
-
- call-generate-readme-workflow:
- if: github.event_name == 'push' || github.event_name == 'workflow_dispatch'
- uses: Keyfactor/actions/.github/workflows/generate-readme.yml@main
+jobs:
+ call-starter-workflow:
+ uses: keyfactor/actions/.github/workflows/starter.yml@3.1.2
secrets:
- token: ${{ secrets.APPROVE_README_PUSH }}
-
- call-update-catalog-workflow:
- needs: call-assign-from-json-workflow
- if: needs.call-assign-from-json-workflow.outputs.update_catalog == 'True' && (github.event_name == 'push' || github.event_name == 'workflow_dispatch')
- uses: Keyfactor/actions/.github/workflows/update-catalog.yml@main
- secrets:
- token: ${{ secrets.SDK_SYNC_PAT }}
\ No newline at end of file
+ token: ${{ secrets.V2BUILDTOKEN}}
+ APPROVE_README_PUSH: ${{ secrets.APPROVE_README_PUSH}}
+ gpg_key: ${{ secrets.KF_GPG_PRIVATE_KEY }}
+ gpg_pass: ${{ secrets.KF_GPG_PASSPHRASE }}
+ scan_token: ${{ secrets.SAST_TOKEN }}
diff --git a/CHANGELOG.md b/CHANGELOG.md
index cdfa877..f6a36ad 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,2 +1,6 @@
-1.0.0
+v1.1.0
+- Modified build to create both .net8 and .net6 versions
+- Modified README to use doctool
+
+v1.0.0
- Initial Version
diff --git a/README.md b/README.md
index dc98db0..8930608 100644
--- a/README.md
+++ b/README.md
@@ -1,156 +1,268 @@
-# Signum Orchestrator Extension
+
+ Signum Universal Orchestrator Extension
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Support
+
+ ·
+
+ Installation
+
+ ·
+
+ License
+
+ ·
+
+ Related Integrations
+
+
-The Signum Orchestrator Extension allows for the Inventorying of Signum private certificates. Discovery, Managment, and ReEnrollment are NOT supported in this integration. A Signum instance must be installed to use this integration along with the ability to consume Signum SOAP-based API endpoints using basic authentication.
+## Overview
-#### Integration status: Production - Ready for use in production environments.
+The Signum Orchestrator Extension supports inventorying certificate stored in a Signum instance. Adding, renewing existing and removing certificates is not supported.
-## 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.
+## Compatibility
-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.
+This integration is compatible with Keyfactor Universal Orchestrator version 10.4.1 and later.
-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.
+## Support
+The Signum Universal Orchestrator extension If you have a support issue, please open a support ticket by either contacting your Keyfactor representative or 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
-## Support for Signum Orchestrator Extension
+Before installing the Signum 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.
-Signum Orchestrator Extension is supported by Keyfactor for Keyfactor customers. If you have a support issue, please open a support ticket with your Keyfactor representative.
-###### 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.
----
+## Create the Signum Certificate Store Type
+To use the Signum Universal Orchestrator extension, you **must** create the Signum Certificate Store Type. This only needs to happen _once_ per Keyfactor Command instance.
-## Keyfactor Version Supported
-The minimum version of the Keyfactor Universal Orchestrator Framework needed to run this version of the extension is 10.4.1
+* **Create Signum using kfutil**:
-## Platform Specific Notes
+ ```shell
+ # Signum
+ kfutil store-types create Signum
+ ```
-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 Renrollment| | |
-|Supports Inventory|✓ |✓ |
+* **Create Signum manually in the Command UI**:
+ Create Signum manually in the Command UI
+ Create a store type called `Signum` with the attributes in the tables below:
-## PAM Integration
+ #### Basic Tab
+ | Attribute | Value | Description |
+ | --------- | ----- | ----- |
+ | Name | Signum | Display name for the store type (may be customized) |
+ | Short Name | Signum | Short display name for the store type |
+ | Capability | Signum | Store type name orchestrator will register with. Check the box to allow entry of value |
+ | Supports Add | 🔲 Unchecked | 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 | 🔲 Unchecked | 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. |
-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 Basic tab should look like this:
-The secrets that this orchestrator extension supports for use with a PAM Provider are:
+ 
-|Name|Description|
-|----|-----------|
-|ServerUsername|The user id that will be used to authenticate to the Signum API endpoints|
-|ServerPassword|The password that will be used to authenticate to the Signum API endpoints|
-
+ #### Advanced Tab
+ | Attribute | Value | Description |
+ | --------- | ----- | ----- |
+ | Supports Custom Alias | Required | 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.) |
-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.
+ The Advanced tab should look like this:
-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
-
+ #### 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:
+ | Name | Display Name | Description | Type | Default Value/Options | Required |
+ | ---- | ------------ | ---- | --------------------- | -------- | ----------- |
+ | ServerUsername | Server Username | The user ID (or PAM key pointing to the user ID) to use with authorization to execute Signum SOAP endpoints in your Signum environment. | Secret | | ✅ Checked |
+ | ServerPassword | Server Password | The password (or PAM key pointing to the password) for the user ID you entered for Server User Name. | Secret | | ✅ Checked |
+ The Custom Fields tab should look like this:
-### 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.
-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"
- }
-~~~
+
-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.
+## Installation
-### 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.
+1. **Download the latest Signum Universal Orchestrator extension from GitHub.**
-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:
+ Navigate to the [Signum Universal Orchestrator extension GitHub version page](https://github.com/Keyfactor/signum-orchestrator/releases/latest). Refer to the compatibility matrix below to determine whether the `net6.0` or `net8.0` asset should be downloaded. Then, click the corresponding asset to download the zip archive.
+ | Universal Orchestrator Version | Latest .NET version installed on the Universal Orchestrator server | `rollForward` condition in `Orchestrator.runtimeconfig.json` | `signum-orchestrator` .NET version to download |
+ | --------- | ----------- | ----------- | ----------- |
+ | Older than `11.0.0` | | | `net6.0` |
+ | Between `11.0.0` and `11.5.1` (inclusive) | `net6.0` | | `net6.0` |
+ | 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` |
+ | `11.6` _and_ newer | `net8.0` | | `net8.0` |
-~~~ json
-{"Secret":"my-kv-secret","Key":"myServerPassword"}
-~~~
+ Unzip the archive containing extension assemblies to a known location.
-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.
-
-
-
-
-
-
----
-
-
-
-## Versioning
-
-The version number of a the Signum Orchestrator Extension can be verified by right clicking on the Signum.dll file in the Extensions/Signum installation folder, selecting Properties, and then clicking on the Details tab.
-
-
-## Signum Orchestrator Extension Installation
-1. Create the Signum certificate store type manually in Keyfactor Command by clicking on Settings (the gear icon on the top right) => Certificate Store Types => Add and then entering the settings described in the next section - Certificate Store Type Settings, OR by utilizing the CURL script found under the Certificate Store Type CURL Script folder in this repo.
-2. Stop the Keyfactor Universal Orchestrator Service for the orchestrator you plan to install this extension to run on.
-3. 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 "Signum" (you may choose to use a different name if you wish).
-4. Download the latest version of the Signum Orchestrator Extension from [GitHub](https://github.com/Keyfactor/signum-orchestrator). Click on the "Latest" release link on the right hand side of the main page and download the first zip file.
-5. Copy the contents of the download installation zip file to the folder created in Step 3.
-6. (Optional) If you decide to create the certificate store type with a short name different than the suggested value of "Signum", edit the manifest.json file in the folder you created in step 3, and modify each "ShortName" in each "Certstores.{ShortName}.{Operation}" line with the ShortName you used to create the certificate store type in Keyfactor Command. If you created it with the suggested value, this step can be skipped.
-7. Start the Keyfactor Universal Orchestrator Service.
-8. In Keyfactor Command, go to Orchestrators => Management and approve the Keyfactor Orchestrator containing the Signum capability that you just installed by selecting the orchestrator and clicking APPROVE.
-
-
-## Certificate Store Type Settings
-Below are the values you need to enter if you choose to manually create the Signum certificate store type in the Keyfactor Command UI (related to Step 1 of Signum Orchestrator Extension Installation above).
-
-*Basic Tab:*
-- **Name** – Required. The display name you wish to use for the new certificate store type. Suggested value - Signum
-- **ShortName** - Required. Suggested value - Signum. If you choose to use a different value, please refer to Step 6 under Signum Orchestrator Extension Installation above.
-- **Custom Capability** - Unchecked
-- **Supported Job Types** - Inventory is the only one that should be checked.
-- **Needs Server** - Checked
-- **Blueprint Allowed** - Checked if you wish to make use of blueprinting. Please refer to the Keyfactor Command Reference Guide for more details on this feature.
-- **Uses PoserShell** - Unchecked
-- **Requires Store Password** - Unchecked.
-- **Supports Entry Password** - Unchecked.
-
-*Advanced Tab:*
-- **Store Path Type** - Fixed (with a value of NA underneath to represent "not applicable")
-- **Supports Custom Alias** - Required
-- **Private Key Handling** - Required
-- **PFX Password Style** - Default
-
-*Custom Fields Tab:*
-None
-
-*Entry Parameters:*
-None
-
-
-## Creating an Signum Certificate Store in Keyfactor Command
-To create a Keyfactor Command certificate store of certificate store type Signum, go to Locations => Certificate Stores and click ADD. Then enter the following:
-- Category - Signum (or the alternate ShortName value you entered when creating your certificate store type).
-- Container - Optional. Refer to Keyfactor Command documentation about this feature.
-- Client Machine - The URL that will be used as the base URL for Signum endpoint calls. Should be something like https://{base url for your signum install}:8888/rtadminservice.svc/basic. The port number of 8888 is a convention that is generally followed in Signum installations, but yours may vary. The "/basic" at the end is required, as this integration makes use of Basic Authentication only when consuming the Signum SOAP API library.
-- Store Path - Not used and hardcoded to NA for "not applicable"
-- Server Username and Server Password - The id/password credentials that have authorization to execute Signum SOAP endpoints in your Signum environment.
-### License
-[Apache](https://apache.org/licenses/LICENSE-2.0)
+ > **Note** If you don't see an asset with a corresponding .NET version, you should always assume that it was compiled for `net6.0`.
+
+2. **Locate the Universal Orchestrator extensions directory.**
+
+ * **Default on Windows** - `C:\Program Files\Keyfactor\Keyfactor Orchestrator\extensions`
+ * **Default on Linux** - `/opt/keyfactor/orchestrator/extensions`
+
+3. **Create a new directory for the Signum Universal Orchestrator extension inside the extensions directory.**
+
+ Create a new directory called `signum-orchestrator`.
+ > The directory name does not need to match any names used elsewhere; it just has to be unique within the extensions directory.
+
+4. **Copy the contents of the downloaded and unzipped assemblies from __step 2__ to the `signum-orchestrator` directory.**
+
+5. **Restart the Universal Orchestrator service.**
+
+ Refer to [Starting/Restarting the Universal Orchestrator service](https://software.keyfactor.com/Core-OnPrem/Current/Content/InstallingAgents/NetCoreOrchestrator/StarttheService.htm).
+
+
+6. **(optional) PAM Integration**
+
+ The Signum 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.
+
+ 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).
+
+
+> 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).
+
+
+
+## Defining Certificate Stores
+
+
+
+* **Manually with the Command UI**
+
+ Create Certificate Stores manually in the UI
+
+ 1. **Navigate to the _Certificate Stores_ page in Keyfactor Command.**
+
+ Log into Keyfactor Command, toggle the _Locations_ dropdown, and click _Certificate Stores_.
+
+ 2. **Add a Certificate Store.**
+
+ 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 "Signum" or the customized certificate store name from the previous step. |
+ | Container | Optional container to associate certificate store with. |
+ | Client Machine | The URL that will be used as the base URL for Signum endpoint calls. Should be something like https://{base url for your signum install}/rtadminservice.svc/basic. The API service port can be configured so yours may use something other than default https/443. The '/basic' at the end is required, as this integration makes use of Basic Authentication only when consuming the Signum SOAP API library. |
+ | Store Path | Not used and hardcoded to NA for 'not applicable' |
+ | Orchestrator | Select an approved orchestrator capable of managing `Signum` certificates. Specifically, one with the `Signum` capability. |
+ | ServerUsername | The user ID (or PAM key pointing to the user ID) to use with authorization to execute Signum SOAP endpoints in your Signum environment. |
+ | ServerPassword | The password (or PAM key pointing to the password) for the user ID you entered for Server User Name. |
+
+
+
+
+ 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 PAM key pointing to the user ID) to use with authorization to execute Signum SOAP endpoints in your Signum environment. |
+ | ServerPassword | The password (or PAM key pointing to the password) for the user ID you entered for Server User Name. |
+
+
+ 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.
+
+ > 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.
+
+
+
+
+
+* **Using kfutil**
+
+ Create Certificate Stores with kfutil
+
+ 1. **Generate a CSV template for the Signum certificate store**
+
+ ```shell
+ kfutil stores import generate-template --store-type-name Signum --outpath Signum.csv
+ ```
+ 2. **Populate the generated CSV file**
+
+ Open the CSV file, and reference the table below to populate parameters for each **Attribute**.
+ | Attribute | Description |
+ | --------- | ----------- |
+ | Category | Select "Signum" or the customized certificate store name from the previous step. |
+ | Container | Optional container to associate certificate store with. |
+ | Client Machine | The URL that will be used as the base URL for Signum endpoint calls. Should be something like https://{base url for your signum install}/rtadminservice.svc/basic. The API service port can be configured so yours may use something other than default https/443. The '/basic' at the end is required, as this integration makes use of Basic Authentication only when consuming the Signum SOAP API library. |
+ | Store Path | Not used and hardcoded to NA for 'not applicable' |
+ | Orchestrator | Select an approved orchestrator capable of managing `Signum` certificates. Specifically, one with the `Signum` capability. |
+ | ServerUsername | The user ID (or PAM key pointing to the user ID) to use with authorization to execute Signum SOAP endpoints in your Signum environment. |
+ | ServerPassword | The password (or PAM key pointing to the password) for the user ID you entered for Server User Name. |
+
+
+
+
+ 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 PAM key pointing to the user ID) to use with authorization to execute Signum SOAP endpoints in your Signum environment. |
+ | ServerPassword | The password (or PAM key pointing to the password) for the user ID you entered for Server User Name. |
+
+
+ > 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.
+
+
+
+ 3. **Import the CSV file to create the certificate stores**
+
+ ```shell
+ kfutil stores import csv --store-type-name Signum --file Signum.csv
+ ```
+
+
+> 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).
+
+
+
+
+
+## License
+
+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/Signum/Signum.csproj b/Signum/Signum.csproj
index bde106d..7747351 100644
--- a/Signum/Signum.csproj
+++ b/Signum/Signum.csproj
@@ -1,19 +1,20 @@
- false
- net6.0
+ true
+ net6.0;net8.0
true
+ disable
-
-
-
-
+
+ Always
+
+
diff --git a/docsource/content.md b/docsource/content.md
new file mode 100644
index 0000000..a0de606
--- /dev/null
+++ b/docsource/content.md
@@ -0,0 +1,7 @@
+## Overview
+
+The Signum Orchestrator Extension supports inventorying certificate stored in a Signum instance. Adding, renewing existing and removing certificates is not supported.
+
+## Requirements
+
+
diff --git a/docsource/images/Signum-advanced-store-type-dialog.png b/docsource/images/Signum-advanced-store-type-dialog.png
new file mode 100644
index 0000000..2b71e8c
Binary files /dev/null and b/docsource/images/Signum-advanced-store-type-dialog.png differ
diff --git a/docsource/images/Signum-basic-store-type-dialog.png b/docsource/images/Signum-basic-store-type-dialog.png
new file mode 100644
index 0000000..7467d15
Binary files /dev/null and b/docsource/images/Signum-basic-store-type-dialog.png differ
diff --git a/docsource/images/Signum-custom-fields-store-type-dialog.png b/docsource/images/Signum-custom-fields-store-type-dialog.png
new file mode 100644
index 0000000..548cb66
Binary files /dev/null and b/docsource/images/Signum-custom-fields-store-type-dialog.png differ
diff --git a/docsource/signum.md b/docsource/signum.md
new file mode 100644
index 0000000..ed37e8e
--- /dev/null
+++ b/docsource/signum.md
@@ -0,0 +1 @@
+## Overview
diff --git a/integration-manifest.json b/integration-manifest.json
index 16867e2..504904f 100644
--- a/integration-manifest.json
+++ b/integration-manifest.json
@@ -8,32 +8,22 @@
"link_github": true,
"update_catalog": true,
"release_dir": "Signum/bin/Release",
+ "release_project": "Signum/Signum.csproj",
"about": {
"orchestrator": {
"UOFramework": "10.4.1",
+ "keyfactor_platform_version": "10.4",
"pam_support": true,
- "win": {
- "supportsCreateStore": false,
- "supportsDiscovery": false,
- "supportsManagementAdd": false,
- "supportsManagementRemove": false,
- "supportsReenrollment": false,
- "supportsInventory": true
- },
- "linux": {
- "supportsCreateStore": false,
- "supportsDiscovery": false,
- "supportsManagementAdd": false,
- "supportsManagementRemove": false,
- "supportsReenrollment": false,
- "supportsInventory": true
- },
"store_types": [
{
"Name": "Signum",
"ShortName": "Signum",
"Capability": "Signum",
- "LocalStore": false,
+ "ServerRequired": true,
+ "BlueprintAllowed": false,
+ "CustomAliasAllowed": "Required",
+ "PowerShell": false,
+ "PrivateKeyAllowed": "Required",
"SupportedOperations": {
"Add": false,
"Create": false,
@@ -41,21 +31,36 @@
"Enrollment": false,
"Remove": false
},
- "Properties": [],
+ "Properties": [
+ {
+ "Name": "ServerUsername",
+ "DisplayName": "Server Username",
+ "Type": "Secret",
+ "DependsOn": "",
+ "DefaultValue": "",
+ "Required": true,
+ "IsPAMEligible": true,
+ "Description": "The user ID (or PAM key pointing to the user ID) to use with authorization to execute Signum SOAP endpoints in your Signum environment."
+ },
+ {
+ "Name": "ServerPassword",
+ "DisplayName": "Server Password",
+ "Type": "Secret",
+ "DependsOn": "",
+ "DefaultValue": "",
+ "Required": true,
+ "IsPAMEligible": true,
+ "Description": "The password (or PAM key pointing to the password) for the user ID you entered for Server User Name."
+ }
+ ],
"EntryParameters": [],
+ "ClientMachineDescription": "The URL that will be used as the base URL for Signum endpoint calls. Should be something like https://{base url for your signum install}/rtadminservice.svc/basic. The API service port can be configured so yours may use something other than default https/443. The '/basic' at the end is required, as this integration makes use of Basic Authentication only when consuming the Signum SOAP API library.",
+ "StorePathDescription": "Not used and hardcoded to NA for 'not applicable'",
"PasswordOptions": {
"EntrySupported": false,
"StoreRequired": false,
"Style": "Default"
- },
- "StorePathType": "",
- "StorePathValue": "na",
- "PrivateKeyAllowed": "Required",
- "JobProperties": [],
- "ServerRequired": true,
- "PowerShell": false,
- "BlueprintAllowed": false,
- "CustomAliasAllowed": "Required"
+ }
}
]
}
diff --git a/readme-src/readme-pam-support.md b/readme-src/readme-pam-support.md
deleted file mode 100644
index d40c73f..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 to the Signum API endpoints|
-|ServerPassword|The password that will be used to authenticate to the Signum API endpoints|
-
diff --git a/readme-src/store-types-tables.md b/readme-src/store-types-tables.md
deleted file mode 100644
index bfd0e07..0000000
--- a/readme-src/store-types-tables.md
+++ /dev/null
@@ -1,50 +0,0 @@
-
-### Signum Store Type
-#### kfutil Create Signum Store Type
-The following commands can be used with [kfutil](https://github.com/Keyfactor/kfutil). Please refer to the kfutil documentation for more information on how to use the tool to interact w/ Keyfactor Command.
-
-```
-bash
-kfutil login
-kfutil store - types create--name Signum
-```
-
-#### UI Configuration
-##### UI Basic Tab
-| Field Name | Required | Value |
-|-------------------------|----------|-------------------------------------------|
-| Name | ✓ | Signum |
-| ShortName | ✓ | Signum |
-| Custom Capability | | Unchecked [ ] |
-| Supported Job Types | ✓ | Inventory, |
-| Needs Server | ✓ | Checked [x] |
-| Blueprint Allowed | | Unchecked [ ] |
-| Uses PowerShell | | Unchecked [ ] |
-| Requires Store Password | | Unchecked [ ] |
-| Supports Entry Password | | Unchecked [ ] |
-
-
-
-##### UI Advanced Tab
-| Field Name | Required | Value |
-|-----------------------|----------|-----------------------|
-| Store Path Type | | na |
-| Supports Custom Alias | | Required |
-| Private Key Handling | | Required |
-| PFX Password Style | | Default |
-
-
-
-##### UI Custom Fields Tab
-| Name | Display Name | Type | Required | Default Value |
-| -------------- | -------------------- | ------ | -------- | ------------- |
-
-
-**Entry Parameters:**
-
-Entry parameters are inventoried and maintained for each entry within a certificate store.
-They are typically used to support binding of a certificate to a resource.
-
-|Name|Display Name| Type|Default Value|Required When |
-|----|------------|-----|-------------|--------------|
-
diff --git a/readme_source.md b/readme_source.md
deleted file mode 100644
index b685aa3..0000000
--- a/readme_source.md
+++ /dev/null
@@ -1,54 +0,0 @@
-
-## Versioning
-
-The version number of a the Signum Orchestrator Extension can be verified by right clicking on the Signum.dll file in the Extensions/Signum installation folder, selecting Properties, and then clicking on the Details tab.
-
-
-## Signum Orchestrator Extension Installation
-1. Create the Signum certificate store type manually in Keyfactor Command by clicking on Settings (the gear icon on the top right) => Certificate Store Types => Add and then entering the settings described in the next section - Certificate Store Type Settings, OR by utilizing the CURL script found under the Certificate Store Type CURL Script folder in this repo.
-2. Stop the Keyfactor Universal Orchestrator Service for the orchestrator you plan to install this extension to run on.
-3. 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 "Signum" (you may choose to use a different name if you wish).
-4. Download the latest version of the Signum Orchestrator Extension from [GitHub](https://github.com/Keyfactor/signum-orchestrator). Click on the "Latest" release link on the right hand side of the main page and download the first zip file.
-5. Copy the contents of the download installation zip file to the folder created in Step 3.
-6. (Optional) If you decide to create the certificate store type with a short name different than the suggested value of "Signum", edit the manifest.json file in the folder you created in step 3, and modify each "ShortName" in each "Certstores.{ShortName}.{Operation}" line with the ShortName you used to create the certificate store type in Keyfactor Command. If you created it with the suggested value, this step can be skipped.
-7. Start the Keyfactor Universal Orchestrator Service.
-8. In Keyfactor Command, go to Orchestrators => Management and approve the Keyfactor Orchestrator containing the Signum capability that you just installed by selecting the orchestrator and clicking APPROVE.
-
-
-## Certificate Store Type Settings
-Below are the values you need to enter if you choose to manually create the Signum certificate store type in the Keyfactor Command UI (related to Step 1 of Signum Orchestrator Extension Installation above).
-
-*Basic Tab:*
-- **Name** – Required. The display name you wish to use for the new certificate store type. Suggested value - Signum
-- **ShortName** - Required. Suggested value - Signum. If you choose to use a different value, please refer to Step 6 under Signum Orchestrator Extension Installation above.
-- **Custom Capability** - Unchecked
-- **Supported Job Types** - Inventory is the only one that should be checked.
-- **Needs Server** - Checked
-- **Blueprint Allowed** - Checked if you wish to make use of blueprinting. Please refer to the Keyfactor Command Reference Guide for more details on this feature.
-- **Uses PoserShell** - Unchecked
-- **Requires Store Password** - Unchecked.
-- **Supports Entry Password** - Unchecked.
-
-*Advanced Tab:*
-- **Store Path Type** - Fixed (with a value of NA underneath to represent "not applicable")
-- **Supports Custom Alias** - Required
-- **Private Key Handling** - Required
-- **PFX Password Style** - Default
-
-*Custom Fields Tab:*
-None
-
-*Entry Parameters:*
-None
-
-
-## Creating an Signum Certificate Store in Keyfactor Command
-To create a Keyfactor Command certificate store of certificate store type Signum, go to Locations => Certificate Stores and click ADD. Then enter the following:
-- Category - Signum (or the alternate ShortName value you entered when creating your certificate store type).
-- Container - Optional. Refer to Keyfactor Command documentation about this feature.
-- Client Machine - The URL that will be used as the base URL for Signum endpoint calls. Should be something like https://{base url for your signum install}:8888/rtadminservice.svc/basic. The port number of 8888 is a convention that is generally followed in Signum installations, but yours may vary. The "/basic" at the end is required, as this integration makes use of Basic Authentication only when consuming the Signum SOAP API library.
-- Store Path - Not used and hardcoded to NA for "not applicable"
-- Server Username and Server Password - The id/password credentials that have authorization to execute Signum SOAP endpoints in your Signum environment.
-### License
-[Apache](https://apache.org/licenses/LICENSE-2.0)
-