readme/changelog

Keyfactor · Apr 5, 2024 · 6ee9876 · 6ee9876
1 parent ae90c62
commit 6ee9876
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 2 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -15,4 +15,7 @@
 # 1.0.10
 * Handle change to Sectigo API for organization/department lookups
 # 1.1.0
-* Allow organization name to be provided in the template section of the config
+* Allow organization name to be provided in the template section of the config
+# 1.2.0
+* Allow for blank CN to be provided
+* Fixes for Certificate Authentication
diff --git a/readme_source.md b/readme_source.md
@@ -21,14 +21,18 @@ Additional information about [Sectigo Certificate Manager](https://sectigo.com/k
 * Code Signing
 
 ## Compatibility
-This AnyGateway is designed to be used with version 21.3.2 of the Keyfactor AnyGateway Framework
+This AnyGateway is designed to be used with version 21.3.2 or newer of the Keyfactor AnyGateway DCOM Framework
 
 ## Prerequisites
 
 ### Certificate Chain
 
 In order to enroll for certificates the Keyfactor Command server must trust the trust chain. Once you create your Root and/or Subordinate CA, make sure to import the certificate chain into the Command Server certificate store
 
+### Sectigo Settings
+For each Organization/Department you plan on using through the gateway, in your Sectigo portal, go to that Organization, select Certificate Settings -> SSL Certificates, and check the "Enable Web/REST API" checkbox.  
+In addition, for the admin account you plan to use, make sure it has the API admin type selected in the portal.
+
 ### Migration
 In the event that a system is being upgraded from the Legacy Sectigo CA Gateway (19.4 or older), a migration from the legacy database format to the AnyGateway format will be required.