directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Birch (JIRA)" <>
Subject [jira] Commented: (DIRSTUDIO-327) Repeated searches for complete result set.
Date Thu, 28 Aug 2008 00:23:44 GMT


Jim Birch commented on DIRSTUDIO-327:

Any chance of getting this issue bumped into a close release?  I'm kinda in love with DirStudio
- she's beautiful - but this is putting pressure on the relationship ;-)

The alternate workaround of bumping the server side limit is considered very bad practice:
 This setting will apply to across all controllers in the Active Directory domain so leaves
a lot of targets open to a DoS attack in a corporate situation.   Everything I've seen warns
against it, eg: [,289483,sid68_gci1265206,00.html]
and some management tools automatically flag a server side limit above 1000 an a problem.

I guess there are a lot of other AD ldap users who could use the tool if it has paged search
support.  There's a few here.

I'm not sure about the ApacheDS design philosophy, but paged searched might be a good idea
for ApacheDS too.

The code changes looks well-contained and pretty easy to implement.  It would make the LDAP
implementation more complete.  There's some sample code here, if it helps: [].

I wouldn't want to mess with the code myself but *I'm happy to do some AD testing here.*

> Repeated searches for complete result set.
> ------------------------------------------
>                 Key: DIRSTUDIO-327
>                 URL:
>             Project: Directory Studio
>          Issue Type: Improvement
>    Affects Versions: 1.2.0
>         Environment: Win2k workstation, java 1.6.0_05
>            Reporter: Jim Birch
> Windows servers have a default server side limit of 1000 returned objects.  AFAIK the
normal way of handling this is to detect that a search returns an incomplete result set and
make further requests to span the full result set.
> There appears to be no such capability in dirstudio which makes searching 15K users extremely

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

View raw message