Function use in the IdP

[Brent Putman]

On 11/20/14 6:24 AM, Rod Widdowson wrote:
> Brent,
>
>> Ah, I think I get it now.  You mean a script impl of the
>> Function/Predicate, e.g. a script impl of Function<String,String>, a
>> script impl of Function<XMLObject, Set<String>>, etc.
> To loop back round on this, do you think it's worthwhile constructing a
> Scripted Function<String, String> to be potentially injected into as the
> RequestURLBuilder  into FunctionDrivenDynamicHTTPMetadataResolver ?

Hard to say, it might be useful for somebody.  The IdP custom schema
there is a little different though.  I didn't allow injection of
arbitrary functions - the one you get is determined by the child element
you configure in: Template, Regex, MetadataQueryProtocol, or none.   
Was mirroring the SP's mechanism mostly.  If we want an arbitrary
function, we'd need to model that in the schema too (same issue as
SignatureValidationFilter).

The real question is: do we want to do all of that?  I had in the back
of my mind that we might not necessarily expose all the advanced stuff
via the custom schemas.  If someone wants to do advanced, they switch to
Spring native config for that.  We do still support that for the
metadata stuff, don't we? Or am I mis-remembering?