The LDAP (Lightweight Directory Access Protocol) connector for Jitterbit Harmony Cloud Studio provides an interface for entering user-provided input such as credentials to create an authenticated LDAP connection. That connection provides the foundation to configure associated LDAP connector activities that interact with the connection. Together, a specific LDAP connection and its activities are referred to as an LDAP endpoint.
Supported API Versions and Prerequisites¶
The LDAP connector uses the Apache Directory LDAP API version 1.0.1. This API supports all types of LDAP servers, not just ApacheDS. Refer to the Apache LDAP API 1.0.1 Documentation and documentation on the specific LDAP server for information on the schema fields.
The LDAP connector requires the use of an agent version 10.1 or later. These agent versions automatically download the latest version of the connector when required.
This connector is used to first configure an LDAP connection, establishing access to an LDAP directory server, and then used to configure one or more LDAP activities associated with that connection as a source or target within an operation:
Search Entry: Returns entries in an LDAP endpoint and is intended to be used as a source in an operation.
Add Entry: Adds entries to an LDAP endpoint and is intended to be used as a target in an operation.
Delete Entry: Deletes entries from an LDAP endpoint and is intended to be used as a target in an operation.
Modify Entry: Modifies entries in an LDAP endpoint and is intended to be used as a target in an operation.
This connector is a Connector SDK-based connector, which may be referred to by Jitterbit when communicating changes made to connectors built with the Connector SDK.
Accessing the Connector¶
The LDAP connector is accessed from the design component palette's Connections tab (see Design Component Palette).
If you experience issues with the LDAP connector, these troubleshooting steps are recommended:
Ensure the LDAP connection is successful by using the Test button in the configuration screen. If the connection is not successful, the error returned may provide an indication as to the problem.
Check the operation logs for any information written during execution of the operation.
Enable operation debug logging (for Cloud Agents or for Private Agents) to generate additional log files and data.
If using Private Agents, you can check the agent logs for more information.