This patch has been committed as bug 44645.
-- Seth
Mark Thomas wrote:
Seth Leger wrote:
Hi devs,
I've added support to the JNDIRealm so that a custom
javax.net.SocketFactory can be specified for the JNDI connection.
This is necessary so that you can perform customized SSL negotiation
on the connection. For instance, it allows you to connect to an SSL
server with an invalid, expired, self-signed, or otherwise untrusted
certificate. To do this, you just need to write a
javax.net.ssl.SSLSocketFactory that does not perform the normal
certificate validation during the SSL handshake and then specify the
classname on the new setSocketFactory() call added by this patch.
The patch was made against trunk of Tomcat 6.0.X. If you have any
questions, please feel free to contact me. Thanks!
Patches posted directly to the dev list can get overlooked if someone
doesn't act on them straight away. To protect against this, please
create a bugzilla entry and attach your patch there.
Cheers,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
