OpenSAML how-to: adding transport to context

[Cantor, Scott]

On 5/20/15, 6:14 PM, "Misagh Moayyed" <mmoayyed at unicon.net> wrote:



>Next question: where/how are the signature canonicalization algorithms
>set?

That's one of the SignatureSigningParameters.

Computing the Parameter objects involves feeding a large set of 
Configuration objects from different levels of the system (library 
defaults, global defaults, per-relying party defaults) into a Resolver 
implementation that intelligently combines all of the different parameters 
together to come up with the answer.

org.opensaml.saml.common.profile.impl.PopulateSignatureSigningParameters 
and related classes implement most of this for the IdP but the work is 
done by the implementation of the resolver that gets injected into it.

The library has default Configurations but the IdP redeclares a lot of it 
statically in its Spring files, I think it's in relying-party-system.xml

If you just brute force the Parameters though, nothing prevents that.


-- Scott