Apache + tomcat - request.getRemoteUser() = null?
So, I'm working in an University setting, where someone else has set up Tomcat 4.03 and Apache 1.3 together, with the Apache SSL module and the Apache Kerberos 3rd party module installed. The Kerberos module sets the authenication header w/ a basic attribute and a representation of the kerberos key. It should, in theory, set the request.getRemoteUser() as well, but it is always null. So, the question: Shouldn't Apache set the RemoteUser variable with basic authentication? Shouldn't it be passed in the header to tomcat? Why me? (ok, so that's rhetorical...) Any suggestions? Everything else works fine... Thanks in advance... Mike
Re: Apache + tomcat - request.getRemoteUser() = null?
Oh yes, I left out relevent information... using the modwebapp (warp) connector. Don't know if that changes anything... Mike - Original Message - From: Jacob Kjome [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, November 27, 2002 9:24 PM Subject: Re: Apache + tomcat - request.getRemoteUser() = null? you need to put tomcatAuthentication=false on your jk connector. Jake At 08:51 AM 11/27/2002 -0500, you wrote: So, I'm working in an University setting, where someone else has set up Tomcat 4.03 and Apache 1.3 together, with the Apache SSL module and the Apache Kerberos 3rd party module installed. The Kerberos module sets the authenication header w/ a basic attribute and a representation of the kerberos key. It should, in theory, set the request.getRemoteUser() as well, but it is always null. So, the question: Shouldn't Apache set the RemoteUser variable with basic authentication? Shouldn't it be passed in the header to tomcat? Why me? (ok, so that's rhetorical...) Any suggestions? Everything else works fine... Thanks in advance... Mike -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Apache + tomcat - request.getRemoteUser() = null?
hmm As I understand it, mod_webapp is not being worked on anymore. If it doesn't support the same kind of functionality that mod_jk provides with tomcatAuthentication=false then it probably never will. My recommendation is to move to mod_jk or mod_jk2. I know next to nothing about mod_webapp configuration so I can't help you much there. Jake At 09:31 AM 11/27/2002 -0500, you wrote: Oh yes, I left out relevent information... using the modwebapp (warp) connector. Don't know if that changes anything... Mike - Original Message - From: Jacob Kjome [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, November 27, 2002 9:24 PM Subject: Re: Apache + tomcat - request.getRemoteUser() = null? you need to put tomcatAuthentication=false on your jk connector. Jake At 08:51 AM 11/27/2002 -0500, you wrote: So, I'm working in an University setting, where someone else has set up Tomcat 4.03 and Apache 1.3 together, with the Apache SSL module and the Apache Kerberos 3rd party module installed. The Kerberos module sets the authenication header w/ a basic attribute and a representation of the kerberos key. It should, in theory, set the request.getRemoteUser() as well, but it is always null. So, the question: Shouldn't Apache set the RemoteUser variable with basic authentication? Shouldn't it be passed in the header to tomcat? Why me? (ok, so that's rhetorical...) Any suggestions? Everything else works fine... Thanks in advance... Mike -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Apache + tomcat - request.getRemoteUser() = null?
Thanks for the advice... maybe I can talk our guy into switching... until then, it's time to digest the authorization header... woohoo... what a system! :) Mike - Original Message - From: Jacob Kjome [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, November 27, 2002 9:56 PM Subject: Re: Apache + tomcat - request.getRemoteUser() = null? hmm As I understand it, mod_webapp is not being worked on anymore. If it doesn't support the same kind of functionality that mod_jk provides with tomcatAuthentication=false then it probably never will. My recommendation is to move to mod_jk or mod_jk2. I know next to nothing about mod_webapp configuration so I can't help you much there. Jake At 09:31 AM 11/27/2002 -0500, you wrote: Oh yes, I left out relevent information... using the modwebapp (warp) connector. Don't know if that changes anything... Mike - Original Message - From: Jacob Kjome [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, November 27, 2002 9:24 PM Subject: Re: Apache + tomcat - request.getRemoteUser() = null? you need to put tomcatAuthentication=false on your jk connector. Jake At 08:51 AM 11/27/2002 -0500, you wrote: So, I'm working in an University setting, where someone else has set up Tomcat 4.03 and Apache 1.3 together, with the Apache SSL module and the Apache Kerberos 3rd party module installed. The Kerberos module sets the authenication header w/ a basic attribute and a representation of the kerberos key. It should, in theory, set the request.getRemoteUser() as well, but it is always null. So, the question: Shouldn't Apache set the RemoteUser variable with basic authentication? Shouldn't it be passed in the header to tomcat? Why me? (ok, so that's rhetorical...) Any suggestions? Everything else works fine... Thanks in advance... Mike -- 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]
