Kofax logo

Kofax Insight 6.5.0 Fix Pack 3

Build Date: May 23, 2023

© 2023 Kofax. All rights reserved.
Use is subject to license terms.

Introduction

This ReadMe file contains information on Kofax Insight 6.5.0 Fix Pack 3, along with instructions on how to install the fix pack on the Azure Cloud Services (extended support).

You can install Kofax Insight 6.5.0.3 to resolve the issues listed below.

Note: To install Kofax Insight 6.5.0.3 successfully, an existing full installation of Kofax Insight 6.5.0 is required.

If you need to perform a full product installation, see the Kofax Insight Installation Guide for instructions.

Please note that this fix pack updates all Insight database schema versions, therefore a complete backup of all databases is required (Admin, Meta, Data, Staging and MTAdmin if used).

Issues Resolved in This Fix Pack

1955403: Azure failed to show some logging messages.

1952897: Primary keys on Insight Admin and project Meta databases were not enforced to be unique.

1943096: Insight Installer failed to run after applying service packs 6.5.0.1 and 6.5.0.2.

1939211: Insight Admin Console Data Loader link was broken when "admin" was part of the hostname.

Issues Resolved in Previous Fix Packs

Issues Resolved in Fix Pack 2

1893593: New calendars could not be created in Admin Console.

Issues Resolved in Fix Pack 1

1842389: Azure deployment Extracts feature did not save files to Azure blob storage when the "Save to file" option was enabled.

Enhancements Introduced in This Fix Pack

1959985: Enhanced LDAP search logic by mapping user domains with LDAP search paths.

1956784: Added support for PostgreSQL with Insight as external data source.

PostgreSQL

PostgreSQL was added as an option to the list of Database types in the "New Connection" dialog box.

The provider for the PostgreSQL server can be either "Odbc Provider" or "DSN Provider".

PostgreSQL is supported only as a data source. Running the Insight Administration database on PostgreSQL is not supported.

If you use PostgreSQL data source, ensure that you have the PostgreSQL ODBC driver installed. By default, the ODBC driver name is "PostgreSQL Unicode(x64)" and the port is 5432 (PostgreSQL default).

If you have a different driver name or a different port, you should adjust these values in the Property Panel > Additional string field of the Data Source.

Type the respective part of the ODBC connection string in the Additional string field as follows:

LDAP configuration supported by 6.5.0.3

Starting with Insight 6.3.0, Active Directory authentication is available for all Insight components, including Installation Manager, Scheduler service, and Import and Export utilities. Custom LDAP path entries can be added to the WCFDataService web.config file under the <appSettings> tag.

Prior to version 6.5.0.3, when LDAP paths were configured, the domain part of the authenticating Windows user account was compared to the first key-value pair in the LDAP path after the last slash.

For example, the following LDAP search paths were configured:

	<add key="LDAPPath-1" value="LDAP://gc.adomin.company.com:389/DC=domainA,DC=company,DC=com">
	<add key="LDAPPath-2" value="LDAP://gc.bdomain.company.ctb:389/DC=domainB,DC=company,DC=com">

User account "domainB\user.name" matched "DC=domainB", and LDAPPath-2 was used for the connection. If neither of the specified paths matched, user properties were not collected for this user from the specified LDAP paths.

Notes:

Starting with 6.5.0.3, LDAP path configuration and search logic were improved for user accounts where the domain name of the user account does not match any of the LDAP paths by using the former logic.

A newly introduced filtering method helps to directly associate user domain names with LDAP paths. The filter is optional, and it can be added to the LDAP path configuration value separated by a semicolon (;).


In the following example, the added "FILTER" associates "domainA" users with the LDAP path "LDAP://ldap.domain.com" in the configuration value after the semicolon.

Example:

	<add key="LDAPPath-Corp" value="FILTER=domainA;LDAP://ldap.domain.com" />

An asterisk (*) for FILTER can also be used to match all domain names.

Example:

	<add key="LDAPPath-Corp" value="FILTER=*;LDAP://ldap.domain.com" />

For compatibility reasons, Insight 6.5.0.3 continues to support the former LDAP path matching logic as well, with the exception that the comparison is not made against the value of the first key-value pair after the last slash (/). The first "DC" key-value pair is used instead, after the last slash.


When a matching Filter is explicitly configured for a given domain, it overrides the Filter specified by an asterisk (*).

When a Filter matches the user's domain, paths without a filter are neglected.


Multiple configuration items can define the same Filter, and Insight tries to use these until the first successful connection is made to retrieve user properties.


Example:

	<add key="LDAPPath-Corp1" value="FILTER=domainA;LDAP://ldap.domain.com" />
	<add key="LDAPPath-Corp2" value="FILTER=*;LDAP://gc1.ldap.domain.com:389/DC=ldap,DC=domain,DC=com" />
	<add key="LDAPPath-Corp3" value="FILTER=*;LDAP://gc2.ldap.domain.com:389/DC=ldap,DC=domain,DC=com" />

In this example,

"domainA\user.name" connects to LDAPPath-Corp1.

"domainB\user.name" connects to LDAPPath-Corp2.

"domainB\user.name" connects to LDAPPath-Corp3 only when LDAPPath-Corp2 fails.


Example:

	<add key="LDAPPath-Corp1" value="FILTER=domainA;LDAP://ldap.domain.com" />
	<add key="LDAPPath-Corp2" value="LDAP://ldap.domain.com/DC=ldap,DC=domain,DC=com" />

In this example,

"domainA\user.name" connects to LDAPPath-Corp1.

"domainB\user.name" does not connect to any of the LDAP paths because neither "FILTER=domainA" nor "DC=ldap" matches "domainB".


Example:

	<add key="LDAPPath-Corp1" value="LDAP://domainA.domain.com/DC=domainA,DC=domain,DC=com" />
	<add key="LDAPPath-Corp2" value="FILTER=domainA;LDAP://ldap.domain.com" />

In this example,

"domainA\user.name" connects to LDAPPath-Corp2 because the value with an explicit Filter takes precedence over the value without a Filter.

Applies To

This fix pack is cumulative and includes the resolved issues released in previous Kofax Insight 6.5.0 fix packs.

You can apply this fix pack to update any of the following versions:

Files Included

This fix pack includes the following files:

File name Version
KofaxInsight-6.5.0.3.zip 6.5.0.3
KofaxInsight-6.5.0.3_ForAzure.zip 6.5.0.3

Install This Fix Pack

Use the following procedure to install the fix pack.

  1. Copy the KofaxInsight_6.5.0.3.0.856_x64.msp file provided with this fix pack to the computer where Kofax Insight is installed.
  2. Run this .msp file as Administrator.

Install Insight 6.5.0.3 on Azure

Use the following procedure to install the fix pack on Azure.

  1. Copy the KofaxInsight-6.5.0.3_ForAzure.zip file to your computer.
  2. Make sure that you comply with the requirements described in the "Prerequisites" section of the Kofax Insight Administrator's Guide for Azure.

    Note: The creation of a cloud service is described in this procedure. You do not need to create it beforehand.

  3. Log in to the Azure portal and follow the instructions on the Microsoft Azure pages to create a storage account.
  4. Review the deployment prerequisites for Cloud Services (extended support) and complete the following steps:
    • Create Key Vault and upload the SSL certificate.
    • Create Virtual Network.
  5. Complete the steps described in the "Update the configuration (.cscfg) file" section of the Kofax Insight Administrator's Guide for Azure.
  6. Navigate to Azure portal > Cloud services (extended support). In the Cloud Services (extended support) pane, select Create.

    The creation window opens in the Basics tab.

  7. Complete the fields in the Basics tab:
    1. Set the Cloud service name and select the Region.
    2. Select From local for the Package/configuration/service definition location.
    3. Select Storage account and upload the .cspkg and .csdef files included in the KofaxInsight-6.5.0.3_ForAzure.zip file, as well as the .cscfg file that you prepared in steps 5 and 6.
  8. Proceed to the Configuration tab and complete the fields:
    1. Select the existing Public IP address or create a new one.
    2. Select None for the Swappable cloud service.
    3. Select the Start cloud service check box.
    4. Select the Key vault that you created.
    5. Click Review + create.

      The deployment process may take about 20-30 minutes.

Install Insight 6.5.0.3 on Docker

See the Kofax Insight Installation Guide.

Remove This Fix Pack

Due to database schema changes, removing this fix pack requires restoring all databases (Admin, Meta, Data, Staging and MTAdmin if used).

Use the following procedure to remove the fix pack.

  1. In the Control Panel, start Programs and Features.
  2. Click View installed updates.
  3. On the list of updates, in the Name column, select the item that corresponds to Kofax Insight 6.5.0.3.
  4. Right-click and select Uninstall.
  5. Restore all databases to the state before the upgrade.