Issue #254 has been updated by Frederic Soulier. % Done changed from 20 to 50
The main class and method impacted by this functionnality seems to be the getEntry method of the jndiServices class. The process used to get all the values from the directory is the following : * test if attributename from the searchresult object contain the specific "Range" option * if it contains this option we loop on this attribute until we get the EOF from the directory * After EOF we construct the new complete "member" attribute (containing all values) and add it to the searchresult ---------------------------------------- Feature #254: Add paged-results support in LSC for multi-valued attribute http://tools.lsc-project.org/issues/254 Author: Frederic Soulier Status: New Priority: Normal Assigned to: Frederic Soulier Category: Core Target version: 1.2.x branch Modify LSC in order to query LDAP source (mainly MS AD) and use the paged-result system in order to query entries with multi-valued attributes that contains a lot of values. MS AD (2008R2) limit the number of values returned for a multi-valued attribute. This limit is configurable using the MS AD ntdsutil tool but it can't exceed the hardcoded limit of 5000 values for a multi-valued attribute. This can cause some troubles for AD Groups objects and their multi-valued attribute "member" which can contain more than 5000 members. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
