DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11779>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11779 Coyote AJP 1.3 connector doesn't support tomcatAuthentication="false" Summary: Coyote AJP 1.3 connector doesn't support tomcatAuthentication="false" Product: Tomcat 4 Version: 4.1.9 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Major Priority: Other Component: Connector:Coyote JK 2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] using the Coyote AJP1.3 connector and mod_jk, when I perform BASIC authentication using Apache 2.0.39, I get through Apache, but when I try to make the call to request.getRemoteUser(), all it ever returns is null. When I use the, now deprecated, old AJP1.3 connector with tomcatAuthentication="false", request.getRemoteUser() always gets the user that was logged in through Apache, never null. For this reason, I can't use the Coyote AJP connector. Why is tomcatAuthentication="false" not supported? Is there a replacement for this functionality? The biggest problem is, I can't use the Admin app without the Coyote AJP connector specified because the old connector doesn't support JMX. BTW, I try to get to the Admin app through port 8080 which doesn't get handled by Apache, but directly by Tomcat. Why does one *have* to specify the Coyote AJP connector in order to allow JMX to work when the AJP connector isn't even a factor in connecting to the Admin app through port 8080???? Jake -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>