Search filter script
cantor.2 at osu.edu
Mon May 2 19:51:12 EDT 2016
On 5/2/16, 7:44 PM, "users on behalf of Douglas E Engert" <users-bounces at shibboleth.net on behalf of deengert at gmail.com> wrote:
>"The SearchFilter object provides support for both positional and named parameters.
> Values provided as parameters are escaped according to RFC 2254."
>might help. It looks like you are building a string, then passing it as the value
>to be searched, so the whole string is escaped gets escaped.
>You may need to look at doing something like the "Named" example.
And my suggestion is not workable either, I keep forgetting the Filter templates aren't Velocity-based (yet, there's a RFE for that, IDP-827).
In a nutshell, yes, what it's doing is what I'd expect.
Whether you use positional or named, you can only plug in values, not supply filter operators and syntax. I don't know if there's a way to override the filter mechanism entirely, it would probably involve native Spring and some Java code.
More information about the users