Grouper Users - Open Discussion List

["Crawford, Jeffrey" <>]

Humm, I tried that too, seems to have been ignored by pspng, also on this page it’s listed as an option:

https://spaces.at.internet2.edu/display/Grouper/Grouper+Provisioning:+PSPNG

 

but it seems to have a default so I wonder if the code is “resetting” it.

 

From: Daniel Burtenshaw <>
Date: Thursday, August 29, 2019 at 1:06 PM
To: Greg Haverkamp <>, "Crawford, Jeffrey" <>
Cc: Grouper Users <>, Jeffrey Williams <>
Subject: RE: [Ext] Re: [grouper-users] pspng ldapSearchResultPagingSize doesn't seem to do anything

 

I think that Greg is correct, I’ve used it with success in the ldap connection settings rather than the changelog.consumer settings, so something like:

 

                ldap.personLdap.pagedResultsSize = 1000

 

should work.

 

From: <> On Behalf Of Greg Haverkamp
Sent: Thursday, August 29, 2019 1:48 PM
To: Crawford, Jeffrey <>
Cc: Grouper-Users <>; Jeffrey Williams <>
Subject: [Ext] Re: [grouper-users] pspng ldapSearchResultPagingSize doesn't seem to do anything

 

WARNING: Stop. Think. Read. This is an external email.

I think you want it in your personLdap configuration.  Unless I botched the search, “ldapSearchResultPagingSize” doesn’t exist anywhere in the Grouper repo (in master).

 

However, it does appear to pull the searchResultPagingSize in LdapSystem.java:

  public int getSearchResultPagingSize() {

    Object searchResultPagingSize = getLdaptiveProperties().get("org.ldaptive.searchResultPagingSize");

    return GrouperUtil.intValue(searchResultPagingSize, searchResultPagingSize_default_value);

  }

 

And getLdaptiveProperties should pull that in from your ldap.personLdap.* properties.

 

Greg

 

 

On Thu, Aug 29, 2019 at 11:42 AM Crawford, Jeffrey <> wrote:

The following is what we have, but it’s pretty simple:

 

ldap.personLdap.url = "ldaps://ldap.iam.ucla.edu:636

ldap.personLdap.user = uid=ldappc, dc=some, dc=path

ldap.personLdap.pass = /opt/grpr/grouper.apiBinary/conf/encryptedLDAP.pass

ldap.personLdap.tls = false

ldap.personLdap.countLimit = 1000

ldap.personLdap.timeLimit = 5000

 

From: Jeffrey Williams <>
Date: Thursday, August 29, 2019 at 9:51 AM
To: "Crawford, Jeffrey" <>
Cc: Grouper Users <>
Subject: Re: [grouper-users] pspng ldapSearchResultPagingSize doesn't seem to do anything

 

Can we see your personLdap config?

On Thu, Aug 29, 2019, 11:59 AM Crawford, Jeffrey <> wrote:

I have the following entry in our pspng config, I noticed that on FullSyncer it pages at 100 elements, our system performs better at 1000 so I tried setting the page size, but the LDAP logs still show that it’s paging at 100.

 

Am I using the parameter correctly?

 

changeLog.consumer.pspng_entitlement.class = edu.internet2.middleware.grouper.pspng.PspChangelogConsumerShim

changeLog.consumer.pspng_entitlement.type = edu.internet2.middleware.grouper.pspng.LdapAttributeProvisioner

changeLog.consumer.pspng_entitlement.quartzCron = 0 * * * * ?

changeLog.consumer.pspng_entitlement.retryOnError = true

changeLog.consumer.pspng_entitlement.ldapPoolName = personLdap

changeLog.consumer.pspng_entitlement.provisionedAttributeName = eduPersonEntitlement

changeLog.consumer.pspng_entitlement.provisionedAttributeValueFormat = urn:mace:ucla.edu:entitlement${group.name.replaceAll("^ucla(?::org)?(.*:)app:(.*)$", "$1$2").replaceFirst(":entitlement:",":")}

changeLog.consumer.pspng_entitlement.userSearchBaseDn = ou=people,dc=ucla,dc=edu

changeLog.consumer.pspng_entitlement.userSearchFilter = uclaPPID=${subject.id}

changeLog.consumer.pspng_entitlement.ldapSearchResultPagingSize = 1000

changeLog.consumer.pspng_entitlement.userSearchAttributes = dn,cn,uid,mail,samAccountName,uidNumber,objectClass,uclaPPID

 

Thanks

Jeffrey Crawford