Make X509AuthServlet extensible
Cantor, Scott
cantor.2 at osu.edu
Mon Apr 27 12:35:32 EDT 2015
On 4/27/15, 12:33 PM, "Marvin Addison" <marvin.addison at gmail.com> wrote:
>We have a use case that requires additional certificate validation beyond what X509AuthServlet does. Based on my analysis it looks like the easiest point to add this additional validation is X509AuthServlet. Everything we want to do is truly in addition to what it already does, so it seems reasonable to suggest that the cert validation routine be factored out into a protected method to support extension. Hopefully a diff makes the suggestion clear:
What did you want to do? There's already a hook to supply a TrustEngine, so is it something you could encapsulate into one?
>I realize that this component may be intentionally designed to discourage extension, but I figure it's a reasonable refactoring that increases functionality for minimal investment. Thoughts?
I'm not averse to it, but just wondering if it's actually needed.
-- Scott
More information about the dev
mailing list