[java-identity-provider COMMIT] in /trunk/idp-saml-impl/src: main/java/net/shibboleth/idp/saml/impl/profile/saml1/Sig...

[Cantor, Scott]

On 2/6/14, 7:38 PM, "Brent Putman" <putmanb at georgetown.edu> wrote:
>
>And/or we could have different contexts to hold the data for the
>specific operations, e.g. protocol message signing vs assertion
>signing.  When I did this originally I just did the one
>SecurityParametersContext because I needed something against which to
>code some of the MessageHandlers, but we can certainly revist.
>
>Same thing with the placement of all 4 -Parameters in a single context -
>that was just the simplest thing to do, but we could in theory have a
>distinct context for each one.

Encryption also gets a bit complex (three different types of objects),
plus we had the conditional notion, where it depended on the transport.
Ideally I guess I'd like to bury that as much as we can into "setup"
stages so the actions just look for the parameters or do nothing, but I
suspect we'll want to think about different contexts, or maybe
more-descriptively named slots on the one context.

-- Scott