Adding an activation condition to an intercept flow ?

[Cantor, Scott]

On 3/30/16, 12:47 PM, "dev on behalf of Tom Zeller" <dev-bounces at shibboleth.net on behalf of tzeller at dragonacea.biz> wrote:



>Quite doable, but, obviously, the default/system activation condition may change, so ideally the AND would refer to the default/system activation condition (rather than being a copy). But I don’t know how to wire that, especially when the parent flow descriptor is abstract.

Just define the condition the system is using with a well-known bean ID so people can reference it.

I don't actually remember what all of that condition is doing. I know what the second half is about, but what is the NOT part?

>Hope I’m making sense. I’m looking for the least XML to add a custom activation condition to an intercept flow. Any ideas ?

I defined a utility bean for AND to hide the worst of the wiring, you just put in all the conditions to join as constructor arguments.

<bean parent="shibboleth.Conditions.AND">
	<constructor-arg>
		<ref bean="shibboleth.consent.AttributeReleaseCondition"/>
	</constructor-arg>
	<constructor-arg>
		<your condition here>
	</constructor-arg>
</bean>

-- Scott

>