Troubleshooting CCS Connection Issues After Migration to IGA 15.0

Products

• CA Identity Suite

Issue/Introduction

After migrating from Symantec IGA 14.5 to 15.0, the C++ Connector Server (CCS) is unreachable, causing provisioning operations to fail.

Symptoms:

Application is unable to reach the connector server.

Logs may show javax.naming.AuthenticationException or LDAP_INVALID_CREDENTIALS (0x31) errors.

Connection tests, even when using FQDN or IP, fail.

Environment

Migration Path: IGA 14.5 to 15.0
Component: C++ Connector Server (CCS)
Host OS: Windows

Resolution

Followed these steps to reset the environment and configure the non-SSL port:

Verify Port Status: Check if the non-SSL LDAP port (20402) is listening. Run the following command in Command Prompt: netstat -an | findstr 20402

Clean Installation (if necessary): If the service state is inconsistent, perform a clean uninstallation of the C++ Connector Server, then reinstall it to ensure a fresh framework state.

Configure CCS Startup Registry: To ensure the CCS listens on the required port, modify the Windows Registry to include the non-SSL configuration:

Navigate to the CCS startup configuration settings in the Registry.

Append ldap://:20402 to the configuration string.

Restart Service: Restart the C++ Connector Server service.

Verification:

• Port Check: Run netstat -an | findstr 20402 again to verify the port is now successfully listening.
• Connection Test: Attempt a non-SSL connection test using a tool like JXplorer.
• IGA Xpress Console: Ensure the Connector Server configuration is correctly added within the IGA Xpress console.
• Provisioning Manager: Perform a directory search or account operation in the Provisioning Manager to confirm full end-to-end functionality.

 

Additional Information

Note: If non-SSL communication is not required, ensure the non-SSL port (20402) is disabled by removing the ldap://:20402 entry from the registry for security best practices.