Hi
I need to extend (tweak) a few behaviors in
org.apache.catalina.valves.CertificatesValve without
having to recompile TC. Is there a way to configure TC
to use a custom CertificateValve?
TC 4.x currently allows a boolean flag to indicate whether or
not the HTTPS port 8443 requires not require client cert Auth.
I am in need to have special logic in there to dynamiccaly
request client cert under certain condition. And I can't expose
more than one port! I need to share the same 8443 port for both purposes.
So what I would like to do is
1. extend the CertificatesValve to perform special processing
2. extend the ContextConfig to load my custom CertificatesValve.
3. Configure the server.xml to use my custom ContextConfig
Just curious as to whether or not this is a safe thing to do
and also for compatibility with future TC releases?
Thanks.
==============================
// Instantiate a new CertificatesValve if possible
Valve certificates = null;
try {
Class clazz =
Class.forName("org.apache.catalina.valves.CertificatesValve");
certificates = (Valve) clazz.newInstance();
} catch (Throwable t) {
return; // Probably JSSE classes not present
}
It's theoretically possible to replace ContextConfig
using somthing like this in server.xml:
<Context configClass="my.very.own.ContextConfig" ... />
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
