Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] Search filter for UI

Please Wait...

grouper-users@internet2.edu

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] Search filter for UI


Chronological Thread 
  • From: Gagné Sébastien <sebastien.gagne.2@umontreal.ca>
  • To: "Earl Lewis" <earl.lewis@utah.edu>, <grouper-users@internet2.edu>
  • Subject: RE: [grouper-users] Search filter for UI
  • Date: Fri, 24 May 2013 08:27:59 -0400
  • Authentication-results: sfpop-ironport04.merit.edu; dkim=neutral (message not signed) header.i=none

Do you want to search cn and sn with wildcards ? e.g.

(&amp;(|(cn=*%TERM%*)(sn=*%TERM%*))(objectClass=person))

 

Otherwise it does look Ok, for reference, here is what we’re using (I do have some spaces between terms, but I don’t think it changes anything) :

<searchType>search</searchType>

     <param>

        <param-name>filter</param-name>

        <param-value>

           (&amp; (|(displayName=*%TERM%*) (sAMAccountName=*%TERM%*)) (&amp;(objectclass=user)(!(objectclass=computer))))

     </param-value>

 

 

De : grouper-users-request@internet2.edu [mailto:grouper-users-request@internet2.edu] De la part de Earl Lewis
Envoyé : 23 mai 2013 18:09
À : <grouper-users@internet2.edu>
Objet : [grouper-users] Search filter for UI

 

We're trying to setup searching subjects within the UI (version 2.1.3) )via something other than the subject ID. We've been messing around with the search filter in sources.xml for our LDAP subject source, as shown here: 

 

<!-- use the firstlastfilter to allow: last, first lookup -->

<!-- what we show should presumably search both the cn and sn for the input value -->

    <search>

       <searchType>search</searchType>

         <param>

            <param-name>filter</param-name>

            <param-value>

            (&amp;(|(cn=%TERM%)(sn=%TERM%))(objectClass=person))

            </param-value>

        </param>

        <param>

            <param-name>scope</param-name>

            <param-value>SUBTREE_SCOPE</param-value>

        </param>

         <param>

            <param-name>base</param-name>

            <param-value>ou=people,dc=testad,dc=utah,dc=edu</param-value>

        </param>

    </search>

 

We had some luck with it at one point but we cannot replicate that again, after many many configuration edits. :( Is this the right place to be doing this? If so, anyone have any idea what we might be doing wrong? 

 

If this isn't enough information I will be glad to send whatever else may help.

 

Earl

earl.lewis@utah.edu

801-581-3635 (office)

801-554-3596 (mobile)




Archive powered by MHonArc 2.6.16.

Top of Page