You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Georg Henzler (JIRA)" <ji...@apache.org> on 2010/11/11 16:39:22 UTC
[jira] Created: (CAMEL-3329) LDAP Component doesn't support Paging
LDAP Component doesn't support Paging
-------------------------------------
Key: CAMEL-3329
URL: https://issues.apache.org/activemq/browse/CAMEL-3329
Project: Apache Camel
Issue Type: Improvement
Reporter: Georg Henzler
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.
[jira] Commented: (CAMEL-3329) LDAP Component doesn't support
Paging
Posted by "Georg Henzler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63285#action_63285 ]
Georg Henzler commented on CAMEL-3329:
--------------------------------------
Yes, you can assign it to me!
> LDAP Component doesn't support Paging
> -------------------------------------
>
> Key: CAMEL-3329
> URL: https://issues.apache.org/activemq/browse/CAMEL-3329
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-ldap
> Affects Versions: 2.5.0
> Reporter: Georg Henzler
> Fix For: Future
>
>
> 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.
[jira] Updated: (CAMEL-3329) LDAP Component doesn't support Paging
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-3329:
-------------------------------
Component/s: camel-ldap
Affects Version/s: 2.5.0
Fix Version/s: Future
> LDAP Component doesn't support Paging
> -------------------------------------
>
> Key: CAMEL-3329
> URL: https://issues.apache.org/activemq/browse/CAMEL-3329
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-ldap
> Affects Versions: 2.5.0
> Reporter: Georg Henzler
> Fix For: Future
>
>
> 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.
[jira] Commented: (CAMEL-3329) LDAP Component doesn't support
Paging
Posted by "Georg Henzler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63267#action_63267 ]
Georg Henzler commented on CAMEL-3329:
--------------------------------------
ALUI Directory Server != Apache Directory Server
> LDAP Component doesn't support Paging
> -------------------------------------
>
> Key: CAMEL-3329
> URL: https://issues.apache.org/activemq/browse/CAMEL-3329
> Project: Apache Camel
> Issue Type: Improvement
> Reporter: Georg Henzler
>
> 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.
[jira] Commented: (CAMEL-3329) LDAP Component doesn't support
Paging
Posted by "Johan Edstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63266#action_63266 ]
Johan Edstrom commented on CAMEL-3329:
--------------------------------------
Junit test from apacheDS
http://svn.apache.org/viewvc/directory/apacheds/tags/1.5.5/server-integ/src/test/java/org/apache/directory/server/operations/search/PagedSearchIT.java?view=markup
> LDAP Component doesn't support Paging
> -------------------------------------
>
> Key: CAMEL-3329
> URL: https://issues.apache.org/activemq/browse/CAMEL-3329
> Project: Apache Camel
> Issue Type: Improvement
> Reporter: Georg Henzler
>
> 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.
[jira] Updated: (CAMEL-3329) LDAP Component doesn't support Paging
Posted by "Georg Henzler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
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: https://issues.apache.org/activemq/browse/CAMEL-3329
> 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.
[jira] Resolved: (CAMEL-3329) LDAP Component doesn't support Paging
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-3329.
--------------------------------
Resolution: Fixed
Fix Version/s: (was: Future)
2.6.0
Assignee: Claus Ibsen
trunk: 1035175.
Thanks for the patch and documentation.
> LDAP Component doesn't support Paging
> -------------------------------------
>
> Key: CAMEL-3329
> URL: https://issues.apache.org/activemq/browse/CAMEL-3329
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-ldap
> Affects Versions: 2.5.0
> Reporter: Georg Henzler
> Assignee: Claus Ibsen
> Fix For: 2.6.0
>
> 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.
[jira] Commented: (CAMEL-3329) LDAP Component doesn't support
Paging
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63279#action_63279 ]
Claus Ibsen commented on CAMEL-3329:
------------------------------------
Georg I assume you are working on a patch for this?
> LDAP Component doesn't support Paging
> -------------------------------------
>
> Key: CAMEL-3329
> URL: https://issues.apache.org/activemq/browse/CAMEL-3329
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-ldap
> Affects Versions: 2.5.0
> Reporter: Georg Henzler
> Fix For: Future
>
>
> 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.