Hi, You are right. I've test same versions and i have no good results. It ignores the tomcatAuthentication entry.
Aleix -----Mensaje original----- De: Jacob Kjome [mailto:[EMAIL PROTECTED]] Enviado el: martes, 21 de enero de 2003 22:01 Para: Tomcat Users List Asunto: tomcatAuthentication="false" and getRemoteUser returning null in recent versions of Tomcat Hi, I've found an issue with the CoyteConnector that I'm not sure is a bug. In versions of Tomcat previous to Tomcat-4.1.11, the CoyteConnector didn't support the tomcatAuthentication="false" which is needed to make a call to getRemoteUser() take the authentication information obtained originally via Apache (or other webserver) front end. As of Tomcat-4.1.11 and through, at least Tomcat-4.1.12, adding tomcatAuthentication="false" to the CoyoteConnector works to enable said behavior. However, I've tested both Tomcat-4.1.18 and Tomcat-4.1.19 and both seem to ignore the tomcatAuthentication="false". Based on what Remy says bug 14069 ( http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14069 ), the CoyoteConnector config does not contain any configuration for tomcatAuthentication="false". He suggests putting said config in jk2.properties rather than on the CoyoteConnector config. However, in bug 12196 ( http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12196 ) Denny Dexter states that this doesn't work for him. Furthermore, I am using mod_jk, not jk2. So, if the CoyoteConnector no longer supports tomcatAuthentication="false", what is the working replacement for it in the configuration for either/both mod_jk and jk2? Jake -- Best regards, Jacob mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
