Shibboleth Developers

[Chad La Joie <>]

The condition would use a general purpose language (e.g. javascript, 
Spring Expression Language) and would have access to anything in the 
current request context.  So you could have conditions based on the 
peer's entity ID, or the result of dependent data connectors or 
attribute defintions, etc.

On 5/26/10 10:43 AM, Kristof Bajnok wrote:
> On Wednesday 26 May 2010 14.41.07 Chad La Joie wrote:
> > - Support the conditional evaluation of attribute definitions and data
> > connectors.  In some cases, some users have data connectors that may be
> > very expensive to resolve and so may only want to use them if some
> > condition is true.  This would allow for that.  The default behavior
> > would remain as it is today but people could add a new, optional element
> > giving an evaluation condition.
>
> What kind of conditions are you considering? It's been come up several times
> that a condition on the peer's entityID would be beneficial. Besides, I can
> imagine situations where attribute value matches could be evaluated before
> firing the data connector (though I don't know if it's reasonably easy to
> implement).
>
> All in all: the proposed changes sound very promising.
>
> Kristof

--
Chad La Joie
http://itumi.biz
trusted identities, delivered