OpenSAML how-to: adding transport to context

[Misagh Moayyed]

Great. Moving on:

SAMLMessageSecuritySupport  says:

If (outboundSAML instanceof SignableXMLObject && parameters != null) {
            SignatureSupport.signObject((SignableXMLObject)outboundSAML, 
parameters);
}

Should there be some sort of else/throw clause that would indicate an error, 
in case a signable object is received and with no parameters to sign it?

-----Original Message-----
From: dev [mailto:dev-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Wednesday, May 20, 2015 7:33 AM
To: Shib Dev
Subject: Re: OpenSAML how-to: adding transport to context

On 5/20/15, 11:53 AM, "Misagh Moayyed" <mmoayyed at unicon.net> wrote:



>In the pipeline, where are the set of components/steps that deal with
>signing objects? I see you’re invoking outbound message handlers, and
>having looked at the hierarchy of AbstractMessageHandler, I don’t see
>anything that would help me, say, sign an authn request. There are some
>that validate, but none I have been able to find that actually do.

org.opensaml.saml.common.binding.security.impl.SAMLOutboundProtocolMessageS
igningHandler


>
>To find out how the IdP does that sort of thing, I noticed the creation
>of a security config that is passed along to an MD resolver. What I
>failed to find was the step that actually did the signing of the
>response for instance.

Search for shibboleth.PreEncodeMessageHandler in the SAML flow bean files.

-- Scott


--
To unsubscribe from this list send an email to 
dev-unsubscribe at shibboleth.net