Disabling Paging Support on JNDI Connectors to Resolve Account Truncation Issues

Products

• CA Identity Manager
• CA Identity Suite

Issue/Introduction

This article provides instructions on resolving issues where LDAP connectors fail to retrieve the complete set of accounts, often truncating results (e.g., retrieving only 200 accounts when the total is 470). This behavior is typically caused by active paging support on the JNDI connector.

Environment

Identity Manager 14.x & 15

Cause

Paging support is enabled by default on the JNDI connector, which can interfere with the retrieval of full account lists in certain directory configurations.

• Connector correlation returns fewer accounts than expected (e.g., capping at 200).
• Log files indicate paging activity: DEBUG - VirtualListViewPaging - Request next 200 results: ldaps://xx.xx.xx.xxx:port

Resolution

To resolve account truncation, you must disable paging support on the JNDI connector. Follow these steps:

1. Stop Connector Services: Stop the CA Identity Manager - Connector Server (Java) and CA Identity Manager - Connector Server (C++) services.

2. Locate Configuration: Navigate to the following directory on the Connector Server: [Connector Server Installation Path]\jcs\conf\override\jndi\

3. Prepare Configuration File:

   • Locate the SAMPLE.connector.xml file.
   • Create a copy of this file and rename the copy to connector.xml.

4. Disable Paging Support:

   • Open connector.xml in a text editor.
   • Locate the paging parameter and update it as follows:

     <paging-supported>false</paging-supported>

   • Save and close the file.

5. Restart Services: Restart the CA Identity Manager - Connector Server (Java) and CA Identity Manager - Connector Server (C++) services to apply the changes.

Additional Information

Performance Tuning for Provisioning - 14.5

 

Performance Tuning for Provisioning - 15.0