tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 12196] - request.getRemoteUser() returns null for AJP request with remote username
Date Wed, 30 Oct 2002 17:30:00 GMT
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=12196>.
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=12196

request.getRemoteUser() returns null for AJP request with remote username

ddexter@lincom-asg.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |



------- Additional Comments From ddexter@lincom-asg.com  2002-10-30 17:29 -------
As mentioned in http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14069
"You should use jk2.properties to set tomcatAuthentication. There's no
"tomcatAuthentication" field on the CoyoteConnector class."

Setting tomcatAuthentication=false in the jk2.properties file does not
fix the problem of request.getRemoteUser() returning null when using the
isapi_redirector2.dll with IIS 5.0.  I have also tried
tomcatAuthentication=0 and tomcatAuthentication=1 with no success.

I set tomcatAuthentication=false in the jk2.properties file, restarted
the "Apache Tomcat 4.1" service, and this was the settings in the
jk2.properties.save file:

#AUTOMATICALLY GENERATED
#Wed Oct 30 10:50:46 CST 2002
secure=false
tomcatAuthentication=false
soTimeout=20000
port=8009
jkHome=D\:\\Tomcat4.1
maxThreads=75
backlog=10
timeout=20000
tcpNoDelay=true

I have "Integrated Windows Authentication" enabled, and anonymous access
disabled on the "jakarta" virtual directory that points to
"D:\Tomcat4.1\bin" where the isapi_redirector2.dll file resides.

The Authenticaion header, as reported by tomcat 4.1.14, is
"Negotiate ELSKVI...slflSdf" and request.getRemoteUser() returns null.

Using Tomcat 4.0.4, and the older JK isapi_redirect.dll, I am able to get
a remote username with the same IIS 5.0 settings.

I have searched through the tomcat-dev and tomcat-user mailing list archives
and I can not find any documentation on the use of the tomcatAuthentication
parameter in the jk2.properties file, other than what was reported in
Bug 14069.

In addition, the JK2 documentation does not mention the use of the
tomcatAuthentication parameter either.  I have checked the documentation for
the new JK 2.0.1 ISAPI redirector at
http://jakarta.apache.org/builds/jakarta-tomcat-
connectors/jk2/release/v2.0.1/doc/
And I have checked the Tomcat 4.1 JK documentation at
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/index.html

This bug (getRmoteUser() returning null) has been reported fixed since 4.1.11,
but only against an Apache/AJP setup.

I believe that it is not fixed for a IIS5/AJP setup when using JK2.

--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message