Kofax eCopy ShareScan 6.5 Fix Pack 4

• when the connector profile was configured with multiple destinations using the 'Connector' type,
• when the connector profile used the 'Destination list' type having at least one destination with the 'Connector' type,
• after importing such connector profile containing at least one destination using the 'Connector' type.

Certain users could not log in to Token Vault if they did not have the necessary permissions for the following Active Directory container or if this container did not exist:

CN=Users,DC=<user's domain name specified on the Token Vault login page>,DC=com

To solve this issue, perform the following configuration steps:

1. Add the "DirectoryAccess" and "Domains" sections before the "Logging" section, as in the example below, in the Token Vault appsettings.json file to specify the domain settings to be used for validating the user belonging to different domains at the login.

   Domain settings:

       Name:          The name of the domain specified by users on Token Vault login screen.

       BaseDN:       The Base DN or context to be used for validating user.

       UserName:   The name of the user to access the directory service for user validation.

       Password:     The password of the user to access the directory service.

   UserName and Password are only required when users has no permission to access the container specified in BaseDN setting.
   
   If Token Vault users belong to different domains, you should specify new domain settings section for each domain.

   An example for 3 domains:

   "DirectoryAccess": {
       "Domains": [
           {
               "Name": "first",
               "BaseDN": "CN=Users,DC=first,DC=domain,DC=com"
               "UserName": "john.doe",
               "Password": "Pwd19_20"
           }, 
           {
               "Name": "other.domain.com",
               "BaseDN": "DC=other,DC=domain,DC=com",
           },
           {
               "Name": "other2.domain.com",
               "BaseDN": "DC=other2,DC=domain,DC=com",
           },
       ]
   }
   

2. Restart Token Vault Windows service