<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 6/18/14 7:50 PM, Brent Putman wrote:<br>
</div>
<blockquote cite="mid:53A225B4.3010100@georgetown.edu" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<br>
Yes, seems natural. Am I inferring then that you think the
preferred way would be to switch gears and use the
SignatureTrustEngine on the SignatureValidationParameters? I'm
sure that's doable in the signature handlers, but in looking at
them it's not as trivial as I'd hoped, because of the way the
generic TrustEngine-oriented superclasses are written.<br>
</blockquote>
<br>
Of course, if we did a complete 180, and completely removed the
trust engine that is set on the handlers in favor of the
SignatureValidationParameters from the message context, refactored
the base classes, etc, that would simplify things considerably.<br>
<br>
If we did that, presumably we'd have to define some sort of new
-Configuration, -Parameters and -Resolver to handle the client cert
case using a cert TrustEngine.<br>
<br>
<br>
<br>
</body>
</html>