OpenSAML how-to: adding transport to context

[Brent Putman]

On 5/19/15 8:50 AM, Cantor, Scott wrote:
> I don't think anything in OpenSAML is prescriptive about how you want to implement your software design.

I'd agree, although there is a certain design and intended usage behind
the messaging API stuff.

>
> In the IdP, a ProfileRequestContext is itself an InOutOperationContext and we bootstrap it at the beginning of each webflow.

I think would be the same in a non-SWF impl.  Conceptually it's pretty
simple.

>
> An SP, which I haven't even thought about with this design, would have different requirements and probably only implements half-duplex context trees that either end with requests or start with responses, except for Logout or a couple of other rarely implemented protocols.


There's a similar problem with a client side impl like the SOAP
client.  Some of the code that exists for things like resolving
signature validation stuff is written as ProfileAction and assumes a
PRC, so isn't directly usable for a client-side use case.  (This is the
other major outstanding issue with completing the SOAP client, the
other being client TLS. I'll be sending out another note about this). 
I was going to look at whether it was feasible to refactor that stuff
to be based purely on a IOOC, with the existing ProfileActions simply
delegating somehow to the new components.  Otherwise we're going to
have to duplicate code.

I guess if we're going to get serious about a Java SP impl, we should
factor that use case into all designs as well.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20150519/28842261/attachment.html>