Topic for tomorrow : InitializeOutboundMessageContext

[Cantor, Scott]

On 2/6/14, 8:24 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:

>I am fairly confused over how and where to instantiate and populate
>the following contexts :

I can take a stab.

>SAMLPeerEntityContext

I think this is done in something like the Initialize action you're
talking about, by copying data from the inbound copy.

> SAMLEndpointContext
> SAMLBindingContext

The only part of this I think would be set in Initialize is the relay
state in the SAMLBindingContext, by copying it from the inbound version,
and this is aided by helper methods in the SAMLBindingSupport helper class.

I'm not sure what would call setIntendedDestinationEndpointURIRequired.
That, I guess is meant to distinguish non-SOAP from SOAP cases, but I
don't really know what code would be expected to know how to set it.

The endpoint context and most of the binding context are set in a separate
(IMHO) action that does the endpoint computation and validation steps
using inbound message fields and metadata, mostly through the
BasicEndpointSelector class.

> SecurityParametersContext

Whatever versions of this exist and get created are done by some other
action that's using a TBD resolver class that computes the data.

-- Scott