Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] Select LDAP filter for auto-completion

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] Select LDAP filter for auto-completion

Chronological Thread 
  • From: Pascal Rigaux <>
  • To:
  • Subject: Re: [grouper-users] Select LDAP filter for auto-completion
  • Date: Thu, 17 Dec 2015 13:34:16 +0100

I confirm it works with this modification :)

Other issues:
- we did not have a maxPageSize param for our LDAP source
- even with maxPageSize, our LDAP does not index for sub queries shorter than
4 chars.
Possible solution: set a timeLimit on binddn on LDAP server side, but that
would be fragile...

Pascal Rigaux.

On 17/12/2015 09:56, Pascal Rigaux wrote:
Looking at the code, I'd suggest:

@@ -115,7 +115,7 @@ public class DojoComboLogic {
String groupIdOrName = query.endsWith("*") ? query.substring(0,
query.length()-1) : query;
if (!StringUtils.isBlank(groupIdOrName)) {

- T t = dojoComboQueryLogic.lookup(request, grouperSession, query);
+ T t = dojoComboQueryLogic.lookup(request, grouperSession,
if (t != null) {

Let's compile this and see if it helps...

On 16/12/2015 15:17, Chris Hyzer wrote:
Searching by identifier needs to return one value, you shouldn’t have a *

Secondly, I would think the freeform searches though should return subjectId,
and if it is found by subjectId, then it wouldn’t even search by identifier,
though you should fix the above problem anyways.


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

On Behalf Of Pascal Rigaux
Sent: Wednesday, December 16, 2015 4:40 AM

Subject: Re: [grouper-users] Select LDAP filter for auto-completion


After double checking, the new UI is really doing a
searchSubjectByIdentifier (?!).

More precisely, when entering "rigaux" in autocomplete (see
screenshot, but in french):
- an ajax call to "addMemberFilter" is done with name "rigaux*"
- in serviceLogic/, method "lookup" in "addMemberFilter"
is calling SubjectFinder.findByIdOrIdentifier
- our "searchSubjectByIdentifier" is doing (uid=%TERM%) which triggers
(uid=rigaux*) whereas uid is indexed only EQ here.

AFAIK we have mostly vanilla grouper & grouper.ui 2.2.1 on all this stuff.

Am I missing something??

Pascal Rigaux.

Chris Hyzer
a écrit :

The UI does a "search" when doing autocomplete on subjects... see
the demo server. You can search on id, name, etc.

You will have to give a screenshot and a lot more details. It is
currently not possible to change the filter for the autocompletes...
but since search is what you want, and it is what it does, we should
be good.

More details... the autocomplete UI control have a display label,
and a value label. When the auto complete displays results, it does
a "search", but then it returns the label as the subject
description, and the value is the sourceId and subjectId. When the
selected item is submitted, then it looks up that subject by the
subjectId (or identifier), which is why you might be seeing that
query on the LDAP server. You might want to use GSH to figure out
your subject source before checking the UI


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

On Behalf Of Guillaume
Sent: Friday, November 20, 2015 9:00 AM

Subject: [grouper-users] Select LDAP filter for auto-completion

Hi everyone,

I would like to configure Grouper UI 2 to use a specific LDAP filter for
auto-completion (for example when adding a member to a group).
Apparently, my current configuration is using the searchType
"searchSubjectByIdentifier" in source.xml but I would like to use the
searchType "search" instead. Is it possible to change it?

Thank you

Guillaume Fay

Pascal Rigaux

Expert en développement et déploiement d'applications
DSIUN-SAS (service applications et services numériques)
Université Paris 1 Panthéon-Sorbonne - Centre Pierre Mendès France (PMF)
B 407 - 90, rue de Tolbiac - 75634 PARIS CEDEX 13 - FRANCE
Tél : 01 44 07 86 59

Archive powered by MHonArc 2.6.16.

Top of Page