Some SAML 1 flow questions

[Tom Zeller]

There will only be one SAML 1 flow, correct ?

I am not sure how to handle the non-SAMLObject inbound message unique
to the SAML 1 flow. In the InitializeOutboundMessageContext action,
which I mocked up based on the testbed's
PrepareOutboundMessageContext, I guess it is easy enough to check for
the IdPInitiatedSSORequest as the inbound message via instanceof in
the action doPreExecute() method, but maybe that code should be
injected.

So, I guess my question is : should the uniqueness of the SAML 1 flow
be coded inside actions or somehow via Spring wiring ?

And as a follow up, do we think we will have both SAML 1 and 2
versions of the InitializeOutboundMessageContext action ?

Thanks.