Changes in behavior
This topic describes behavior that differs from the previous version of Kofax Communications Manager.
Extended use of HTTPS Protocol for KCM installations
With this version, all communication with the KCM installation will be encrypted using HTTPS protocol. To ensure secure communication, the public certificate of the server must include the external host name of the server in the allowed DNS of its Subject Alternative Name. Moreover, internal communication within the KCM installation will also utilize the HTTPS protocol, requiring an internal certificate with the internal host name of the server in the allowed DNS of its Subject Alternative Name.
TLS 1.3 support between Contract Manager and Instances
KCM supports several versions of the TLS (Transport Layer Security) protocol for encrypted connections, including TLS 1.1, TLS 1.2, and TLS 1.3. Now by default, the TLS 1.1, TLS 1.2, and TLS 1.3 is used if none are specified.
Changes to Upgrade process for KCM installations
The upgrade process has been modified to incorporate inherited internal and private port ranges, as well as Java and Tomcat installations, from the previous KCM installation, unless explicitly overwritten. In this manner, the new installation will make use of any previously configured settings without requiring manual input.
Shared resources are not longer controlled by ManageCM
The previous ManageCM parameter /SetSharedResource has been removed. Setting the location of shared resources can be done using the Upgrade.exe or AddContractManager.exe tool with the parameter ContractManager!SharedResourceLocation.
Changed default Data Backbone name
The new default name of the data backbone is now Data_Backbone instead of Test.
Improved data processing with asynchronous file logging
The KCM installation and configuration tools now utilize asynchronous file logging so that the logging process runs independently. As a result, users can expect smoother and more seamless interactions with the tools, leading to increased productivity and efficiency.
MakePDFDocument exit point changed
The default implementation of the MakePDFDocument now calls ContractDocToPDF by default.
Change to the ITP Admin account
For new installations of KCM, the Designer no longer contains the default ITP Admin account. The existing ITP Admin accounts will remain after KCM upgrades. These existing ITP Admin accounts can now be deleted and purged manually.
Changes in Designer for Windows
Designer for Windows no longer allows selection of Lotus Notes, AS/400, or Mainframe in the Add New Module dialog. The KCM Core Administrator does not support selecting these platforms in the Add Module dialogue. As a result, the Lotus Notes dll is no longer a part of the shipment.
Web Application security enhanced by removing ActiveX controls for IE11
To further improve the security of our web application, we have removed the ActiveX files from the sample web application and the Designer. In Designer, all code related to ActiveX functionality has been removed. This reduces the risk of security breaches.