The ldap component allows you to perform searches in LDAP servers using filters as the message payload.
This component uses standard JNDI (
javax.naming package) to access the server.
Maven users will need to add the following dependency to their
pom.xml for this component:
The ldapServerBean portion of the URI refers to a DirContext bean in the registry. The LDAP component only supports producer endpoints, which means that an
ldap URI cannot appear in the
from at the start of a route.
You can append query options to the URI in the following format,
The base DN for searches.
Specifies how deeply to search the tree of entries, starting at the base DN. Value can be
no paging used
Camel 2.6: When specified the ldap module uses paging to retrieve all results (most LDAP Servers throw an exception when trying to retrieve more than 1000 entries in one query). To be able to use this a LdapContext (subclass of DirContext) has to be passed in as ldapServerBean (otherwise an exception is thrown)
depends on LDAP Server (could be all or none)
Camel 2.6: Comma-separated list of attributes that should be set in each entry of the result
The result is returned in the Out body as a
ldap:ldapserver, references a Spring bean with the ID,
ldapserver bean may be defined as follows:
The preceding example declares a regular Sun based LDAP
DirContext that connects anonymously to a locally hosted LDAP server.
Following on from the Spring configuration above, the code sample below sends an LDAP request to filter search a group for a member. The Common Name is then extracted from the response.
If no specific filter is required - for example, you just need to look up a single entry - specify a wildcard filter expression. For example, if the LDAP entry has a Common Name, use a filter expression like:
Binding using credentials
A Camel end user donated this sample code he used to bind to the ldap server using credentials.