Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] grouperClient and LDAP search scope

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] grouperClient and LDAP search scope

Chronological Thread 
  • From: "Hyzer, Chris" <>
  • To: Marwan Shaher <>, "" <>
  • Subject: RE: [grouper-users] grouperClient and LDAP search scope
  • Date: Thu, 28 Apr 2016 17:53:08 +0000
  • Accept-language: en-US
  • Authentication-results: Colorado.EDU; dkim=none (message not signed) header.d=none;Colorado.EDU; dmarc=none action=none;
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:23

Its can you fill out a jira and perhaps a pull
request if you have time? :)


-----Original Message-----

On Behalf Of Marwan Shaher
Sent: Thursday, April 28, 2016 1:32 PM

Subject: [grouper-users] grouperClient and LDAP search scope

Is there a way in the groupClient's LDAP operations to set or change the
LDAP search scope? It looks like by default it is set to search one
level (ONELEVEL_SCOPE) of the named context. It would be nice if it
could be set to search an entire subtree (SUBTREE_SCOPE).
Our use case is that our user accounts are contained in one OU, but
there are other OU's that contain service accounts, departmental admin
accounts, etc... All accounts get assigned a unique opaque subject ID,
and it would be helpful for our users to use the grouperClient to do the
subject Id to net Id translation and vise versa.
I've gone through the grouperClient 2.3.0 source code and I could only
see that the search scope is set in the "examples/" and
"examples/". If the solution is to re-compile, is the
scope set elsewhere that I should be aware of?


Marwan Shaher
Identity & Access Management
U. of Colorado Boulder

Archive powered by MHonArc 2.6.16.

Top of Page