SignAssertions action not needed ?

[Cantor, Scott]

On 2/4/14, 12:59 PM, "Brent Putman" <putmanb at georgetown.edu> wrote:

>There's a couple of utility methods there which are somewhat specific to
>the protocol message handling case, operating on MessageContext, but the
>idea would be the same:
>1) Check for and get the  SignatureSigningParameters instance to be used
>(for the profile flow it's TBD where that would live) and
>2) if present, get the Assertion and sign it.  Signing is fairly
>boilerplate.  See any of our signing code, such as in
>SAMLMessageSecuritySupport.signMessage(messageContext).

I wasn't sure how finished the parameter classes/interfaces were, I'm
still unclear on what's finished and what's still TBD. I guess you're
saying the parameters themselves are done, but the code that would serve
them up after factoring in various inputs is the part that's TBD.

-- Scott