Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 55330 invoked from network); 2 Apr 2002 02:10:15 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 2 Apr 2002 02:10:15 -0000 Received: (qmail 20393 invoked by uid 97); 2 Apr 2002 02:10:02 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 20362 invoked by uid 97); 2 Apr 2002 02:10:01 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 20349 invoked from network); 2 Apr 2002 02:10:00 -0000 Date: Mon, 1 Apr 2002 18:10:01 -0800 From: Jakarta Tomcat Newsgroup (@Basebeans.com) Message-Id: <200204020210.g322A1s29275@basebeans.com> To: tomcat-user@jakarta.apache.org Subject: Re: HELP!! Container managed authentication problem with Apache 1.3 + Tomcat 4 + Warp X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Subject: Re: HELP!! Container managed authentication problem with Apache 1.3 + Tomcat 4 + Warp From: "Hyunjin Kim" === uh oh... I just found out that tomcat example application's security stuff works fine from port 80. That means the apache-tomcat connection was not the problem... I also found out that the username/password combination defined in /jakarta-tomcat/conf/tomcat-users.xml works(go through the authentication with role defined in that tomcat-users.xml file). and that doesn't make sense.... here's my server.xml for the application i am developing: I haven't deleted the section that came with server.xml file, but it said realm from lower level would override the global one.. so.. this should work right?? (Of course it works when called from stand alone tomcat...) and my web.xml for my application(jakarta-tomcat/webapp/nanoenc/WEB-INF/web.xml): Intranet Security Constraint /intranet/* employee administrator FORM default /login.jsp /loginerror.jsp I think I am very close... but no cigar yet.. I need to have apache understand that I am going to use different authentication method for context "nanoenc". (it might be impossible for me to fix this without changing code for warp or tomcat.. i guess..) If you give me any idea or helping hand, I will really appreciate. Thank you!! -- To unsubscribe: For additional commands: Troubles with the list: