TrustEngine refactoring

[Brent Putman]

On 8/15/14 8:01 PM, Cantor, Scott wrote:
> On 8/15/14, 7:48 PM, "Brent Putman" <putmanb at georgetown.edu> wrote:
>> As-is, it's gonna break stuff in the IdP when I check it in.  Some tests
>> certainly, maybe some compile, not sure.  Would you like me to check-in
>> what I have and let it break, and we fix as necessary? If so, since
>> we're into the weekend, do you want me to wait until Monday or just do
>> it now?  Or me take a stab at fixing it all up myself in one go?  I know
>> some of the latter, but I don't think I know where everything is
>> config-wise.
> I'm ok if you want to break it, or if you want to try fixing some of it.

I'll just go ahead and check it in.  The existing wiring at least should
be easy to fix.

>> The X509 stuff in particular is going to require new action(s) and/or
>> adding stuff to existing actions to invoke the new
>> X509CredentialValidationParametersResolver to populate the
>> X509CredentialValidationParameters on the
>> X509CredentialSecurityParametersContext on the MessageContext (whew).
> Yes, it's just a copy of PopulateSignatureValidationParameters I think.
>

Ah, ok. 

In hindsight, I'm thinking that perhaps some/all of the new X509 stuff
should be renamed to reflect that it's really about client cert TLS
validation, not some general X509Credential validation.  But probably
better to check-in and then rename.