The LDAP Server Connector accepts an LDAP connection request from an LDAP client on a well-known port set up in the configuration (usually 389). You can know further about this using the information provided here.
The LDAP Server Connector only operates in Server mode, and spawns a copy of itself to take care of any accepted connection until the connection is closed by the LDAP client.
This Connector can be used in conjunction with the IBM® Password Synchronization plug-ins. For more information about installing and configuring the IBM Password Synchronization plug-ins, please see the Password Synchronization Plug-ins.
Each LDAP message received on the connection drives one cycle of the LDAP Server Connector logic. The main thread returns to listening for similar LDAP requests from other LDAP clients. At this point, Attribute Mapping will take place, and the appropriate attributes like the LDAP Operation should be mapped into the work object.
The rest of the AssemblyLine will be executed, and when the cycle reaches the Response channel the return message is built from Attributes mapped out, and sent back to the client. If it was an LDAP search command, the user will call the add method to build the data structure that is to be sent back to the client. The LDAP Server Connector goes back to listening for the next LDAP command on the existing connection.
The value of the LDAP operation is provided in the LDAP.operation attribute in the LDAP Server Connector conn entry, which should be mapped into the work entry for further processing (along with any other required attributes). Legal values are SEARCH, BIND, UNBIND, COMPARE, ADD, DELETE, MODIFY, and MODIFYRDN. The LDAP message provides a number of attributes for the specified LDAP operation.