TrustEngine refactoring

[Cantor, Scott]

On 8/20/14, 9:18 PM, "Brent Putman" <putmanb at georgetown.edu> wrote:
>
>The only question I had about the Spring/SWF stuff was:  I added the new
>PopulateClientTLSValidationParameters action into DecodeMessage in
>saml-abstract-flow.xml, so it's running for all the SAML flows right
>now.  I wanted to have it only run for the SOAP flows, but I couldn't
>immediately see how to do that.  Is there an existing place by which
>that can be accomplished?  I don't grok all the bean layout and flow
>composition yet.  I tried adding to soap-security-flow.xml, but that
>didn't work and I think I understand why.

That one runs later as the inbound subflow, what used to be the security
policy. I don't know, does the populate action have to complete before the
subflow runs? I wouldn't necessarily have thought so but I haven't
reviewed the changes.

Which is the first action or handler that relies on the context being
populated?

We have some options anyway, like attaching a condition predicate that
checks the binding, or various fun tricks that can be played like defining
the same bean name in every flow but turning it into a no-op in some of
them.

The way flows compose is that all the beans get put into a blender, and
the beans defined/imported by the abstract or parent flow(s) get
overridden by beans defined closer to the concrete flow definition. That
allows for a lot of overriding.

-- Scott