Grouper Users - Open Discussion List

["Black, Carey M." <>]

Liam,

 

I also found have found this page to be very, very helpful.

 

And I did, and expected, the same thing from this page as you did.

                I removed the “silly default values” in the three searches then added a value to one search I wanted to test.

                For me, this results in an LDAP timeout error being logged, and the UI behaves fairly badly under those conditions.

 

So, I would go one step farther with this request.

 

I think that the search should only be done if the user provided an input for that search.

                I suspect there is no valid ( useful, meaningful, diagnostic )  reason for a “empty value” search to be done. ( The UI appears to wait till you have 2 or 3 characters before it will do a search. )

                If I am correct, then I think it should be considered an error for the search to be performed without any input value(s), and that should be guarded against/prevented.

 

--

Carey Matthew

 

From: [mailto:] On Behalf Of Liam Hoekenga
Sent: Thursday, March 30, 2017 4:28 PM
To:
Subject: [grouper-users] LDAP "Free form search" issue in the Subject API Diagnostics

 

The answer from one of my earlier questions pointed me at the "Subject API Diagnostics", which seems like a really useful tool.

 

I think it would be useful to be able to perform any of the searches via the diagnostic tool on it's own.  It's actually the first thing I tried to do.

 

I found if you do provide terms for a single search, it runs all of the defined searches with incomplete search terms.  Mostly harmless.

 

With the provided LDAP searches, you can get sort of useless value match searches, but those return quickly..

 

    (&(exampleEduRegId=)(objectclass=exampleEduPerson))

    (&(uid=)(objectclass=exampleEduPerson))

 

The problem is the freeform search.  If you don't provide a string for the freeform search, you can get a wildcard search like...

 

    (&(|(|(uid=)(cn=*))(exampleEduRegId=))(objectclass=exampleEduPerson))

 

...which returns every exampleEduPerson object in the search base.  Looking at the filter, I get why it's doing it, but it's not what I expected.

 

I know you can provide default search terms in subjects.properties / sources.xml, but I think this tool would be useful for debugging issues with any given subject, using whatever piece of identifying information is handy.

 

Liam