camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Georg Henzler (JIRA)" <>
Subject [jira] Updated: (CAMEL-3329) LDAP Component doesn't support Paging
Date Sun, 14 Nov 2010 18:39:24 GMT


Georg Henzler updated CAMEL-3329:

    Attachment: patch.txt

Patch for the camel-ldap component that introduces two new options:

|| Name ||	Default 	||Description||
|pageSize |	no paging used |  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)   |
|returnedAttributes| depends on LDAP Server (could be all or none) | Comma-separated list
of attributes that should be set in each entry of the result |

> LDAP Component doesn't support Paging
> -------------------------------------
>                 Key: CAMEL-3329
>                 URL:
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-ldap
>    Affects Versions: 2.5.0
>            Reporter: Georg Henzler
>             Fix For: Future
>         Attachments: patch.txt
> When retrieving many users from an LDAP server, an LDAP error is thrown  "Ldap error
4 Size Limit Exceeded". This can sometimes be configured on the LDAP server, but in my case
the limit is fixed and set to 1000 (ALUI Directory Server doesn't seem to support changing
this setting).
> As a workaround PagedResultsControl in combination with LdapContext could be used if
a parameter "pageSize" is given in the endoint url.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message