scripted conditions for intercept flows

[Cantor, Scott]

On 12/6/18, 2:00 PM, "users on behalf of Liam Hoekenga" <users-bounces at shibboleth.net on behalf of liamr at umich.edu> wrote:

> Is "input" set to anything for "shibboleth.Conditions.Scripted" (specifically for context based intercept flows)?

shibboleth.Conditions.Scripted is a shortcut for 
<bean id="shibboleth.Conditions.Scripted"
        class="net.shibboleth.idp.profile.logic.ScriptedPredicate" abstract="true" /> (see system/conf/utilities.xml)

That gets you to the Javadoc to answer your question as what its type is and what by definition "input" is going to be set to, which is ProfileRequestContext in this and most other cases.

That means it's usable when it's injected into a property that takes a Predicate<ProfileRequestContext> and that's what "input" is going to be set to.

> Any pointers for accessing attributes / values in this situation?

There are built-in classes (subclasses of the base class at [1]) for looking at attributes without any scripts, one of which is already in the context-check flow configuration in comments and then there's [2] describing the general contract of interceptors and what the tree looks like.

All of it is linked to the javadocs (the boxes in the wire diagrams in [2] all link to the corresponding class documentation).

-- Scott
[1] http://shibboleth.net/cgi-bin/java-idp.cgi/net.shibboleth.idp.profile.logic.AbstractAttributePredicate
[2] https://wiki.shibboleth.net/confluence/display/IDP30/ProfileHandling