LogoutPropagationFlowDescriptor API Changes

[Marvin Addison]

>
> The main reason I kept the activationCondition property in place was
> because it lets the deployer attach additional constraints on the bean
> alongside the "built-in" behavior.
>

I attempted to preserve that flexibility via a new component that suited
both use cases better in my view, Function<SPSession,
LogoutPropagationFlowDescriptor> that is pluggable. I provided a "default"
implementation in LogoutPropagationFlowDescriptorSelector. In any case it's
important that the bean definition used in both the UI and the propagation
flow is the same.

The trouble with using a Predicate<ProfileRequestContext> in both places is
that it's oriented to switching on context-tree data, which felt awkward in
the UI. Doable, of course, but awkward. What I came up with, which is
admittedly different from other flows, works well for this case.

M
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20151006/5c3adfab/attachment.html>