https://bz.apache.org/bugzilla/show_bug.cgi?id=55770
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bz.apache.org/bugzilla/show_bug.cgi?id=55770
--- Comment #4 from Christopher Schultz ---
SSLServerSocketFactory doesn't have any methods that allow us to replace the
SSLContext, and neither does JSSESocketFactory. I think we have to re-bind to
the port in order to actually change anything
https://bz.apache.org/bugzilla/show_bug.cgi?id=55770
--- Comment #3 from Mark Thomas ---
The solution is to replace the SSLContext. That should be fairly simple for
JSSE. It is a little more 'interesting' for OpenSSL since you need to destroy
the SSLContext and you can't do that while it is in us
https://issues.apache.org/bugzilla/show_bug.cgi?id=55770
--- Comment #2 from Christopher Schultz ---
It turns out this is something of a mess. During initialization, the connector
(really o.a.t.util.net.jsse.JSSESocketFactory) sets-up a set of TrustManager
objects in an array, which are passed-in
https://issues.apache.org/bugzilla/show_bug.cgi?id=55770
--- Comment #1 from Christopher Schultz ---
For the JSSE connector, it appears that changing the TrustManager itself is
non-trivial: it would require that the SSLServerSocketFactory be re-built from
scratch, the connector would have to deta
