VERIFIED SOLUTION i

Resolve incorrect entry for tls.version property in EngageOne Server


 

Issue

The EngageOne Server v4.4 deploy.properties file contains the tls.version property as below:

#Default TLS protocol if ssl enabled. Values can be TLSv1, TLSv1.1, TLSv1.2
#tls.version=TLSv1.2


During the configuration steps of the eos.groovy file, when this property has an invalid value, the configuration process finishes with no errors and hence resulting in the system not working properly. 


 

Cause

This was identified as a defect in the eos.groovy configuration process.
 

Resolution

UPDATED: April 26, 2018
Validation rule for tls.version property are now added in EngageOne Server v4.4SP4 and later releases.

So when an incorrect value is provided for the property #tls.version, the configuration process will fail with an error and the recommended valid values for this property are included in the log file to enable the user specify the correct value.