Yes and I agree with the limit for a single call. The load in the LDAP server could be a problem. In our case we need, because a user have several objects (n) with several permissions/operations (m) over the same object, the call to LDAP need to retrieve n x m items.
Nuno Miquelina -----Original Message----- From: Emmanuel Lécharny <[email protected]> Sent: 29 de julho de 2019 16:58 To: [email protected] Subject: Re: Using REST to query more than 1000 entries Keep in mind that most of the existing LDAP server are configured by default to return a limited number of results (typically 1000). There is generally no valid reason to get past this number (typically, it will pound your server, and most of the time, you won't need that many elements). So think about it twice if you want to get that many elements from your database : do you *really* need them ? On 29/07/2019 17:54, Nuno Miquelina wrote: > 1000 is a considerable number, but for large implementations it's always a > limit. > And can fool the user about the number of entries that they have on the > database (LDAP). Is not critical but is important to browse all the records > that LDAP have registered. > > Nuno Miquelina > > -----Original Message----- > From: Shawn McKinney <[email protected]> > Sent: 29 de julho de 2019 16:30 > To: [email protected] > Subject: Re: Using REST to query more than 1000 entries > > > >> On Jul 29, 2019, at 10:21 AM, Nuno Miquelina <[email protected]> >> wrote: >> >> Also, at site level (fortress web), the limit is reached and a message is >> displayed saying that is showing the first 1000 items. There is no way (that >> we have seen) to get the remaining results. > Are you able to work around this issue, perhaps by narrowing down the search? > Trying to understand the severity of this limitation. > > Thanks, > —Shawn > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
