Finalizing TrustEngine config

[Cantor, Scott]

On 6/19/14, 9:37 AM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:

>This is somewhat tangentially related.
>
>Brent and I discussed this some time ago. We need a centralized placed to
>pull together the default key info providers.
>
>Currently the custom schema parsers create this list by hand, and I see an
>equivalent list in relying-party-system.xml.  I'm guessing that the trust
>engines Scott is talking of adding will need them too.

The common factor seems to be the default list, independent of what
they're being loaded into, because that part is different in each case.

Basically this:

<util:list>
<bean 
class="org.opensaml.xmlsec.keyinfo.impl.provider.RSAKeyValueProvider" />
<bean 
class="org.opensaml.xmlsec.keyinfo.impl.provider.DSAKeyValueProvider" />
<bean 
class="org.opensaml.xmlsec.keyinfo.impl.provider.DEREncodedKeyValueProvider
" />
<bean 
class="org.opensaml.xmlsec.keyinfo.impl.provider.InlineX509DataProvider" />
                        </util:list>


>Would it be sensible to create a single centralized bean with this in?  If
>so, where and what do we call it?

It would depend on what needs it. Right now, I use it in
relying-party-system.xml, and my hope was to move the trust engine config
there as well.

If the custom parser you mean is the RelyingParty one, that means we'd
need it in the profile-defaults config. Is that it?

-- Scott