Basicauth (#39)

* Allow use of basic auth only

* Trim all leading 0s when searching by serial number

* Update readme and changelog

* Update generated README

Author: dgaley

CHANGELOG.md

@@ -1,15 +1,19 @@
-1.0.4
+1.0.4  
 -Inital Release.  Support for Enroll, Sync, and Revocation. 
 
-1.0.5
--Fixes for Renewal Due To Api Validation Issues (Renewals can't send validation flag into Api)
+1.0.5  
+-Fixes for Renewal Due To Api Validation Issues (Renewals can't send validation flag into Api)  
 -Added Trace Logging for troubleshooting
 
-1.0.6
+1.0.6  
 -Sync fix - certs pending in Entrust now return External Validation status
 
-1.0.7
+1.0.7  
 -Add configuration option to skip expired certs on sync
 
-1.0.8
--Fixed logging bug when no SANs were present in request
+1.0.8  
+-Fixed logging bug when no SANs were present in request
+
+1.1.0  
+-Added support for basic auth (no client certificate)  
+-Fixed an issue with cert lookups when the serial number has leading 0s

README.md

@@ -14,6 +14,14 @@ This repository contains an AnyGateway CA Connector, which is a plugin to the Ke
 
 # Introduction
 This AnyGateway plug-in enables issuance, revocation, and synchronization of certificates from Entrust's Managed SSL/TLS offering.  
+
+# Entrust Authentication
+Entrust API now supports two methods of authentication:  
+1. Basic Auth only  
+2. Basic Auth + Certificate Auth
+
+When creating your API user name and password in the Entrust portal, you will be given the option to select a certificate to go with it. If you do select a certificate, then the gateway will require that certificate information to connect. Otherwise, do not provide ClientCertificate information to the gateway.
+
 # Prerequisites
 
 ## AnyGateway Platform Minimum Version
@@ -161,7 +169,7 @@ This is the username for the gateway to use to authenticate to Entrust
 * ```AuthPassword```
 This is the password for the account the gateway should use to authenticate to Entrust
 * ```ClientCertificate```
-The location and thumbprint of the client authentication certificate to use to connect to Entrust 
+(OPTIONAL) The location and thumbprint of the client authentication certificate to use to connect to Entrust 
 * ```Name```
 The default requester name.
 * ```Email```

readme_source.md

@@ -1,5 +1,13 @@
 # Introduction
 This AnyGateway plug-in enables issuance, revocation, and synchronization of certificates from Entrust's Managed SSL/TLS offering.  
+
+# Entrust Authentication
+Entrust API now supports two methods of authentication:  
+1. Basic Auth only  
+2. Basic Auth + Certificate Auth
+
+When creating your API user name and password in the Entrust portal, you will be given the option to select a certificate to go with it. If you do select a certificate, then the gateway will require that certificate information to connect. Otherwise, do not provide ClientCertificate information to the gateway.
+
 # Prerequisites
 
 ## AnyGateway Platform Minimum Version
@@ -147,7 +155,7 @@ This is the username for the gateway to use to authenticate to Entrust
 * ```AuthPassword```
 This is the password for the account the gateway should use to authenticate to Entrust
 * ```ClientCertificate```
-The location and thumbprint of the client authentication certificate to use to connect to Entrust 
+(OPTIONAL) The location and thumbprint of the client authentication certificate to use to connect to Entrust 
 * ```Name```
 The default requester name.
 * ```Email```