Release Notes > Summer 2016 - June > LDAP Connector
  

LDAP Connector

After You Upgrade

Configure the Java Heap Size for LDAP Connector

If you increased the Java heap size to accommodate memory requirements to read or write binary data or large amounts of data with LDAP Connector in a previous version, perform the following steps after the upgrade:

Copy the Certificates for LDAP Connections Enabled with Secure Connection

After you upgrade LDAP Connector, the Secure Agent does not retain the certificates available in the following directories from the previous version:
The Secure Agent also does not retain the certificates placed in the cacerts file in the following directory from the previous version:
<Secure Agent installation directory>\jre\lib\security\cacerts file
The issue causes the Data Synchronization tasks and mapping tasks to fail after the upgrade.
To ensure that the tasks do not fail, perform the following tasks:
You must restart the Secure Agent after you copy the certificates and files.

LDAP Connector Fixed Limitations

Review the Release Notes of previous releases for information about previous fixed limitations.
The following table describes fixed limitations:
CR
Description
ICS-6458
Secure connection fails when you configure the LDAP connection for one-way SSL communication as you cannot delete the keystore file, truststore file, and password in the connection properties.

LDAP Connector Known Limitations

The following table describes known limitations:
CR
Description
INFA 430196
Metadata search fails when the distinguished name (DN) has a space or a special character. You can however include special characters, such as comma, underscore, and =.
Workaround: Remove the space or unsupported character before you fetch the metadata.
INFA 429082
The LDAP Connector does not support proxy servers and communicates with the LDAP server directly.
ICS-3081
When you use an LDAP object as a target, the target statistics generated for affected rows and applied rows is incorrect.
ICS-2239
Even though you have the option to configure a lookup for an LDAP object, lookup is not supported for LDAP connector.
CON-4544
When you run a task to delete user data from the LDAP server, and if the distinguished name has special characters, the row statistics displayed is incorrect even though the delete operation succeeds.
CON-3881
If you use an LDAP secure connection with custom certificates in a task to read data from or write data to an LDAP server, the connection fails when the version of the Secure Agent is 30.0 or later. The error occurs if the server certificates are not available in the latest <Secure Agent installation directory> main\tomcat and <Secure Agent installation directory>\main\rdtm directories.
Workaround: Place the server certificates in the latest rdtm and Tomcat directories of the Secure Agent installation.
CON-2385
You cannot apply pushdown optimization for an LDAP source.
CON-2384
When you set parameters for an LDAP source in an advanced filter, the Secure Agent uses the parameter name as a string and passes it as a value in the condition instead of resolving the parameter.
CON-2382
You cannot apply an advanced filter for an LDAP source if the LDAP connection is fully parameterized.
CON-2313
The Base DN does not appear as a mandatory field in the LDAP connection. When you do not specify the base DN, the Secure Agent fails to fetch the metadata.
CON-2310
You cannot preview data for both an LDAP source and target. The Show Data Preview icon that appears on the Target tab of a Data Synchronization task is not applicable.
CON-2257
For large binary data and data precision that is equal to or more than 10 MB, the Secure Agent fails to apply the update strategies on the LDAP target.