Provide LDAP search paging and callback handling support
--------------------------------------------------------
Key: JS2-1171
URL: https://issues.apache.org/jira/browse/JS2-1171
Project: Jetspeed 2
Issue Type: Improvement
Components: LDAP, Security
Affects Versions: 2.2.1
Reporter: Ate Douma
Assignee: Ate Douma
Fix For: 2.2.1
To be able to sustain (very) large LDAP trees for security mapping and
synchronisation the LDAP searches need to be possibly paged and processed from
a callback handler instead of of loading (and mapping) all results upfront.
Spring LDAP (1.3.0) does provide basic support for using a LDAP
PagedResultsControl and callback handlers, which is what we will leverage here
through a new PagedSearchExecutor component.
The standard Spring LDAP callback handling though does not support "aborting"
or stopping search processing, nor does it provide access to the current
search/paging processing state.
A more specialised (and Generics supporting) SearchResultHandler interface and
default (base) implementations will be provided instead which also is LDAP
independent, e.g. also usable for other type of (mapping) back-ends like JCR.
Note: to be able to use/set LDAP DirContext PagedResultsControl a Spring
MutablePoolingContextSource is now required instead of plain
PoolingContextSource.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
