Update generated README

Author: Keyfactor

README.md

@@ -1,27 +1,34 @@
-# Windows IIS Orchestrator
+# Windows IIS Binding Orchestrator
 ## Orchestrator
 
-The IIS-With-Bindings AnyAgent allows a user to create, configure, and manage a Keyfactor certificate store defined as an Internet Information Systems (IIS) binding definition. The certificate itself will still be stored in the defined server's personal certificate store, but the management within Keyfactor will be abstracted to appear as if the binding itself houses the certificate.
+The IIS Bindings orchestrator treats the certificates bound (actively in use) on a Microsoft Internet Information Server (IIS) as a Keyfactor certificate store. Inventory and Management functions are supported. The orchestrator replaces the IIS orchestrator (which did not support binding.)
 
 <!-- add integration specific information below -->
 *** 
-**IIS With Binding AnyAgent Configuration**
+**IIS Binding Orchestrator Configuration**
 
 **Overview**
 
-The IIS-With-Bindings AnyAgent allows a user to create, configure, and manage a Keyfactor certificate store defined as an Internet Information Systems (IIS) binding definition. The certificate itself will still be stored in the defined server&#39;s personal certificate store, but the management within Keyfactor will be abstracted to appear as if the binding itself houses the certificate.
+The IIS Binding Orchestrator remotely manages certificates in a Windows Server local machine certificate store.
+The "Personal" (My) and "Web Hosting" Stores are supported.
+Only certificates that are bound to an IIS web site are managed.
+Unbound certificates are ignored.
 
 This agent implements three job types – Inventory, Management Add, and Management Remove. Below are the steps necessary to configure this AnyAgent.
 
-**1. Create the New Certificate Store Type for the New IIS-With-Bindings AnyAgent**
+WinRM is used to remotely manage the certificate stores and IIS bindings. WinRM must be properly configured to allow
+the server running the orchestrator to manage the server running IIS.
+
+**1. Create the New Certificate Store Type for the IIS Binding Orchestrator**
 
 In Keyfactor Command create a new Certificate Store Type similar to the one below:
 
 #### STORE TYPE CONFIGURATION
 CONFIG ELEMENT	| DESCRIPTION
----------------------|------------------
+------------------|------------------
 Name	|Descriptive name for the Store Type
 Short Name	|The short name that identifies the registered functionality of the orchestrator. Must be IISBinding
+Custom Capability|Store type name orchestrator will register with. Must be "IISBindings".
 Needs Server	|Must be checked
 Blueprint Allowed	|Unchecked
 Requires Store Password	|Determines if a store password is required when configuring an individual store.  This must be unchecked.
@@ -30,7 +37,7 @@ Supports Custom Alias	|Determines if an individual entry within a store can have
 Uses PowerShell	|Unchecked
 Store Path Type	|Determines what restrictions are applied to the store path field when configuring a new store.  This must be Multiple Choice
 Store Path Value|A comma separated list of options to select from for the Store Path. This, combined with the hostname, will determine the location used for the certificate store management and inventory.  Must be My, WebHosting
-Private Keys	|This determines if Keyfactor can send the private key associated with a certificate to the store.  This is requried since IIS will need the private key material to establish TLS connections.
+Private Keys	|This determines if Keyfactor can send the private key associated with a certificate to the store.  This is required since IIS will need the private key material to establish TLS connections.
 PFX Password Style	|This determines how the platform generate passwords to protect a PFX enrollment job that is delivered to the store.  This can be either Default (system generated) or Custom (user determined).
 Job Types	|Inventory, Add, and Remove are the supported job types. 
 
@@ -44,25 +51,16 @@ Job Types	|Inventory, Add, and Remove are the supported job types.
 
 **Custom Fields:**
 
-<table>
-<tr><th>Parameter Name</th><th>Parameter Type</th><th>Default Value</th><th>Required</th></tr>
-<tr><td>spnwithport</td><td>Boolean</td><td>false</td><td>No</td></tr>
+- **SPN With Port** – Defaults to false but some customers need for remote PowerShell Access
 
-- **SPN With Port** – Defaults to false but some customers need for remote Powershell Access
-</table>
+Parameter Name|Parameter Type|Default Value|Required
+---|---|---|---
+spnwithport|Boolean|false|No
 
 ![](images/screen1-b.gif)
 
 **Entry Parameters:**
 This section must be configured with binding fields. The parameters will be populated with the appropriate data when creating a new certificate store.<br/>
-<table>
-<tr><th>Parameter Name</th><th>Parameter Type</th><th>Default Value</th><th>Required</th></tr>
-<tr><td>Port</td><td>String</td><td>443</td><td>Yes</td></tr>
-<tr><td>IP Address</td><td>String</td><td>*</td><td>Yes</td></tr>
-<tr><td>Host Name</td><td>String</td><td></td><td>No</td></tr>
-<tr><td>Site Name</td><td>String</td><td>Default Web Site</td><td>Yes</td></tr>
-<tr><td>Sni Flag</td><td>String</td><td>0 - No SNI</td><td>No</td></tr>
-<tr><td>Protocol</td><td>Multiple Choice</td><td>https</td><td>Yes</td></tr>
 
 - **Site Name** – Required (Adding an entry, Removing an entry, Reenrolling an entry). The site name for the web site being bound to – i.e. &quot;Default Web Site&quot;
 - **IP Address** – Required (Adding an entry, Removing an entry, Reenrolling an entry). The IP address for the web site being bound to. Default is &quot;\*&quot; for all IP Addresses.
@@ -71,19 +69,27 @@ This section must be configured with binding fields. The parameters will be popu
 - *Protocol* - Required (Adding an entry, Removing an entry, Reenrolling an entry) 
    - https
    - http
-- **Sni Flag** – Optional. Set the SNI flag assoicated with the binding being created.Default is &quot;0&quot;. Acceptable values are:
+- **Sni Flag** – Optional. Set the SNI flag associated with the binding being created. Default is "0". Acceptable values are:
    - 0 - No SNI
    - 1 - SNI Enabled
    - 2 - Non SNI Binding
    - 3 - SNI Binding
-</table>
+
+Parameter Name|Parameter Type|Default Value|Required
+---|---|---|---
+Port|String|443|Yes
+IP Address|String|*|Yes
+Host Name |String||No
+Site Name |String|Default Web Site|Yes
+Sni Flag  |String|0 - No SNI|No
+Protocol  |Multiple Choice|https|Yes
 
 ![](images/screen1-c.gif)
 
-**2. Register the IIS-With-Bindings AnyAgent with Keyfactor**
-See Keyfactor InstallingKeyfactorOrchestrators.pdf Documentation.  Get from your Keyfactor contact/representitive.
+**2. Register the IIS Binding Orchestrator with Keyfactor**
+See Keyfactor InstallingKeyfactorOrchestrators.pdf Documentation.  Get from your Keyfactor contact/representative.
 
-**3. Create an IIS With Binding Certificate Store within Keyfactor Command**
+**3. Create an IIS Binding Certificate Store within Keyfactor Command**
 
 In Keyfactor Command create a new Certificate Store similar to the one below, selecting IIS With Binding as the Category and the parameters as described in &quot;Create the New Certificate Store Type for the New IIS-With-Bindings AnyAgent&quot;.