How to extract info from the search filter? about node-ldapjs

[mcavage]

Howdy,

Yeah, perfect - so if they're sending "compound" filters you kind of have to introspect the filter to see what type it is. Here's a complex example of doing it in the riak backend I wrote: https://github.com/mcavage/node-ldapjs-riak/blob/master/lib/search.js#L86

That said, if you're sure they're only going to send and and or filters, just do this:

var address = req.filter.filters && req.filter.filters.length ? req.filter.filters[0].value : req.filter.value;

Basically if it's an and|or filter, it will have a filters property, which is an array, and judging by wat you sent they should be "simple" filters at that point.

You probably don't want to do a regex, in case the value has a whacky character in it. Let me know if that helps.

m

[tttp]

Hi,

actually, my example were incorrect, was xavier* instead of xavier (so that's in initial instead of value). And the one from outlook generated a filters[0].filters...

anyway, went for a regex at the end (yeap I know, now I have two problems ;)

var address = req.filter.toString().match(/(\w.?=(._?)_)/);
and address[1] is so far good enough.

To be continued...

[mcavage]

Hey Xavier,

Well, if it's a substring filter - is it sending *xavier* or xavier*? Basically, you could look at ldapjs/lib/filters/substr_filter.js and grab one of the properties depending on how it's being set. Or just regex ;)

m

[tttp]

Well, if it's a substring filter - is it sending *xavier* or xavier*?

For the autocomplete, it seems to be xavier*. ldap.js is super useful to
check out what the clients send. It seems to be a bit "creative".

Basically, you could look at ldapjs/lib/filters/substr_filter.js and grab
one of the properties depending on how it's being set. Or just regex ;)

So, I'm having it running for a beta and tracking the queries for a while
seeing what I'm catching and what I'm missing... to be continued.

So far, the biggest issue seems to be that some version of thunderbird are
denial of servicing me (firering a ldap query at every keystroket). I'm not
sure if I should skip all queries of less than 2 chars or if I throttle
somehow (eg. queue the queries and don't run the old one if a new one comes
in less than x ms)

Testing...