Grouper Users - Open Discussion List

[Earl Lewis <>]

Pretty sure I've found my problem. When I look at the grouper_members table I can see that search_string0 column only contains my cn value for the person rows. Then search_string1 through search_string4 are all null/empty. Ergo, no search available on anything other than cn. Are my assumptions correct here?

Also, the searchString0 values are all preceded and followed by a comma, presumably to accommodate additional values within that individual search column. Is this being controlled by the subjectVirtualAttrbute_0_searchAttribute0 configuration setting? If not, can someone point me to the right place in the configuration files where this is controlled? 

So I suppose the million dollar question then is this: can I update these values, either directly in the database (or via gsh?) so I can get to where I want to be (either multiple values in search_string0, or values in search_string0 to search_string4)? Or, do I need to  reconfigured the sources.xml and then reload my database via the loader?

And then I suppose I'll also need to make sure the sort_string0 -  sort_string4 should all be populated if I want the sorting to function as expected?

Earl

801-581-3635 (office)

801-554-3596 (mobile)

On 5/24/13 6:27 AM, "Gagné Sébastien" <> wrote:

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 : [] De la part de Earl Lewis
Envoyé : 23 mai 2013 18:09
À : <>
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

801-581-3635 (office)

801-554-3596 (mobile)