Finalizing TrustEngine config

Cantor, Scott cantor.2 at osu.edu
Thu Jun 19 10:45:40 EDT 2014


On 6/19/14, 10:41 AM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:
>
>The constructor for the trust engine (in this case
>org.opensaml.xmlsec.signature.support.impl.ExplicitKeySignatureTrustEngine
>)
>needs a KeyInfoCredentialResolver which is instantiated as "new
>org.opensaml.xmlsec.keyinfo.impl.BasicProviderKeyInfoCredentialResolver
>(that list)" 
>
>In V2 (and currently in V3) that is created on the fly *in the parser*
>which
>is completely against our desire to leave defaulting in the objects or the
>XML.  It might well be that a centrally defined list is not what we need.

Yeah, what bugs me is that of all the options, the one I dislike the most
is hardcoding bean IDs into custom parsing logic.

If we can't default this inside the library itself, none of the options
are very nice when it comes to the custom parsers.

-- Scott




More information about the dev mailing list