https://issues.apache.org/bugzilla/show_bug.cgi?id=44645
Summary: [Patch] JNDIRealm - Doesn't support JNDI
"java.naming.ldap.factory.socket" parameter
Product: Tomcat 6
Version: 6.0.16
Platform: PC
URL: http://java.sun.com/j2se/1.5.0/docs/guide/jndi/jndi-
ldap-gl.html#socket
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
Created an attachment (id=21695)
--> (https://issues.apache.org/bugzilla/attachment.cgi?id=21695)
Patch for JNDIRealm.java
The "java.naming.ldap.factory.socket" JNDI environment parameter is used to
specify the classname of a javax.net.SocketFactory class to be used for all
network connections inside a JNDI context.
This parameter is not supported in the getDirectoryContextEnvironment()
function of JNDIRealm. It was probably overlooked because there is no constant
for it in the JNDI API (for some reason...). This patch adds support for this
parameter to JNDIRealm.
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.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
