Filter templates and multi-valued dependency attributes

[Wessel, Keith]

Thanks, Scott. I assumed that was velocity code inside that template, but I wasn't positive. I'm used to just seeing a single LDAP query in there, at the most using something like the get(0) reference.

So, I guess my question should be how exactly does the filter template work? Does it output a string that gets passed in as the filter to the LDAP query? If I were to, say, make a for loop to iterate over the values of the memberOf attribute, would the contents of that for loop just be another component of the query or'd on to what I already hve? Or would the output be taken as a bunch of separate queries, one from each iteration of the for loop?

Just trying to understand the mechanics of the filter template. Once I understand that, I think I can figure this out.

Keith


-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Wednesday, August 30, 2017 7:47 AM
To: Shib Users <users at shibboleth.net>
Subject: RE: Filter templates and multi-valued dependency attributes

> Is it possible to write a filter template in a chaining data connector that looks
> up multiple values of a dependency attribute and returns the full set of
> results?

I imagine you could use a loop construct in Velocity to build up a filter. As usual, it's probably the commas that will get you.

There's nothing special about an input with multiple values, it's just that the usual filters and queries tend to assume one, and just do get(0) to retrieve it.

-- Scott

-- 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net