Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] LDAP Grouper Loader paging issue

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] LDAP Grouper Loader paging issue


Chronological Thread 
  • From: Shilen Patel <>
  • To: T-Heetderks <>
  • Cc: "" <>
  • Subject: Re: [grouper-users] LDAP Grouper Loader paging issue
  • Date: Fri, 23 Apr 2021 18:20:48 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=duke.edu; dmarc=pass action=none header.from=duke.edu; dkim=pass header.d=duke.edu; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=kQWsITQs17LJ+mbBXP7R5FQuCyyrVgVVrnf8DIbPRDs=; b=ayQql1bJvOnfQ/N5765Pft3n3h+xWDvjg1V3XBxLIGSdPXotZiAOe+lppHVKMTLb50dgR89F3tAUru9MmuMnJKRbxgAuG5nFx1dxPJPTzG+dzX/b7mN3Xp1tJslu2j4jPEPS913Vq8cmCLona/iEkmynsttbY4aPmEEC2hiQdu78viEFnqKf6vT7CLI8DMZ51aHJ8fc0IfiuhEJCtfJiMjoDdE8X8GEcd2iLjRUBmVmlA+LvGXbPqY3bfMsfws+6W08Ihl1GbKtaqzu/fkHDtWV8ghCVpTFHN5a029drLLOEFS/RvuZp3OB8zOdcOF38FsBiAQazZMV0j91/QyZsTw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=nTvZA90jxZVDlh+r4EL2HmqX1Im3xqReoTDAj0QSqhDHemcDQr3JL3g8uQ3XNZDmXrCeogTijC466sXkyqt1uCYaYqaJqDwhqA5J6RYiJXLA2A2dOUEpOTkhapPAiFta2C5jtyFjQJU30eZOxLAUeg7Y+mblTjAdwX4y6vPx+EJOcHJg+mU3PU+ZFkNPfoHJIWz8WywIC4dysdsT7el8IcVZMGxeOV0xNUd3lWlJqh9q5zVlgYM2CdzMlzLlOEZUqJ2S/muvHp+pb7xLNrWpwDUJTg9i9GMBKKR9xMRfnqhNAnYvhsPiVaTH5MHg9jCsQWiZtQW/aDzueBRJ967glQ==

It seems like Grouper is trying to do paging since the logs show the first
query returns 400 results and then the second returns 100.

Are you able to run a command line ldapsearch that has a page size of 400 and
returns more than 500 using the same ldap account? I don’t normally use
openldap but I’m looking at some openldap docs that state the following:

“However, the size limit applies to the total count of entries returned
within the search, and not to a single page.”

Are you able to increase the size limit for the ldap account that grouper is
using?

Thanks!

- Shilen

On 4/23/21, 1:31 PM, " on behalf of
T-Heetderks" < on behalf of
> wrote:

Been having issues trying to get my LDAP Grouper Loader to work.
I don't understand why the paging (via pagedResultsSize) isn't working...
When running the Diagnostic, it connects and queries successfully, but
only
returns the OPENLDAPs transaction limit (500).
The grouper-loader.properties file has:

ldap.enterpriseldap.pagedResultsSize = 400

The OPENLDAP log shows:

slapd[1249]: conn=1553 op=4 SRCH base="ou=people,dc=montana,dc=edu"
scope=2
deref=0 filter="(&(uid=groupersystem)(objectClass=person))"
slapd[1249]: conn=1553 op=4 SRCH attr=cn uniqueIdentifier givenname sn uid
mail
slapd[1249]: conn=1553 op=4 SEARCH RESULT tag=101 err=0 nentries=0 text=
slapd[1249]: conn=1553 op=5 SRCH base="ou=people,dc=montana,dc=edu"
scope=2
deref=0 filter="(&(|(uid=groupersystem)(employeeNumber=groupersystem))
(objectClass=person))"
slapd[1249]: conn=1553 op=5 SRCH attr=cn uniqueIdentifier givenname sn uid
mail
slapd[1249]: <= bdb_equality_candidates: (employeeNumber) not indexed
slapd[1249]: conn=1553 op=5 SEARCH RESULT tag=101 err=0 nentries=0 text=
slapd[1249]: conn=1553 op=6 SRCH base="ou=people,dc=montana,dc=edu"
scope=2
deref=0 filter="(objectClass=person)"
slapd[1249]: conn=1553 op=6 SRCH attr=uniqueIdentifier
slapd[1249]: conn=1553 op=6 SEARCH RESULT tag=101 err=0 nentries=400 text=
slapd[1249]: conn=1553 op=7 SRCH base="ou=people,dc=montana,dc=edu"
scope=2
deref=0 filter="(objectClass=person)"
slapd[1249]: conn=1553 op=7 SRCH attr=uniqueIdentifier
slapd[1249]: conn=1553 op=7 SEARCH RESULT tag=101 err=4 nentries=100 text=

Any help is greatly appreciated!
- Thomas





Archive powered by MHonArc 2.6.24.

Top of Page