Skip to content

Commit 4240c24

Browse files
authored
Update readme_source.md
1 parent 5541dc9 commit 4240c24

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

readme_source.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,14 @@ Entry Parameters|N/A| There are no Entry Parameters
5252
![](Media/Images/CertStoreType-EntryParameters.gif)
5353

5454
**2. Register the A10 vThunder Orchestrator with Keyfactor**
55-
See Keyfactor InstallingKeyfactorOrchestrators.pdf Documentation. Get from your Keyfactor contact/representative.
55+
1. Stop the Keyfactor Universal Orchestrator Service for the orchestrator you plan to install this extension to run on.
56+
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 "vThunderU". You may choose to use a different name, but then you must edit the manifest.json file downloaded from GitHub (Step 3) and modify based on Step 5 below.
57+
3. Download the latest version of the A10 orchestrator extension from [GitHub](https://github.com/Keyfactor/a10vthunder-orchestrator).
58+
4. Copy the contents of the download installation zip file to the folder created in Step 2.
59+
5. (Optional) If you decided to name the folder created in Step 2 to something different than the suggested name (vThunderU), you will need to edit the manifest.json file. Modify "CertStores.{folder name}.Capability" to the folder name you created in Step 2.
60+
6. Start the Keyfactor Universal Orchestrator Service.
61+
62+
Please reference the "Keyfactor Orchestrators Installation and Configuration Guide" obtainable from your Keyfactor contact/representative for more information regarding this step.
5663

5764
**3. Create a A10 vThunder Certificate Store within Keyfactor Command**
5865
In Keyfactor Command create a new Certificate Store similar to the one below

0 commit comments

Comments
 (0)