Page Comparison

...

A Scripted Predicate is instantiated using one of two static factory methods (rather than created directly by invoking a Java constructor), so they have a different syntax in Spring. You can refer to the javadoc for complete details.

<bean id="MyCondition" parent="shibboleth.Conditions.Scripted" factory-method="inlineScript"
		p:customObject-ref="MyCustomObject" p:hideExceptions="true">
    <constructor-arg>
        <value>
        <![CDATA[
			// Your script here
			true;
         ]]>
        </value>
    </constructor-arg>
</bean>

<bean id="MyCondition" parent="shibboleth.Conditions.Scripted" factory-method="resourceScript"
  c:_0="javascript"
  c:_1="%{idp.home}/conf/script.js" />

Alternative Input Types

Most of the conditions used in the IdP configuration tend to be of the signature Predicate<ProfileRequestContext>, which this bean provides. In some unusual cases, a different input type is used. In such cases, this bean can’t be used, but a Java class that is higher up in the class hierarchy can be substituted instead, net.shibboleth.shared.logic.ScriptedPredicate

Using this class is essentially the same as using the parent bean except that the bean declaration contains this:

<bean id="example" class="net.shibboleth.shared.logic.ScriptedPredicate">

instead of:

<bean id="example" parent="shibboleth.Conditions.Scripted">

In addition, adding the property named “inputType” and setting it to a specific class type expected as input will constrain the class and raise an error if an unexpected type is passed into the script.

Reference

...