Return-Path: Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 9311 invoked from network); 20 Mar 2000 13:40:03 -0000 Received: from unknown (HELO dns) (209.14.132.3) by locus.apache.org with SMTP; 20 Mar 2000 13:40:03 -0000 Received: from [216.192.190.27] (jc@thp.org); Mon, 20 Mar 2000 08:38:57 -0500 X-WM-Posted-At: dns; Mon, 20 Mar 00 08:38:57 -0500 Date: Mon, 20 Mar 2000 08:39:12 -0500 Sender: John Coonrod From: John Coonrod To: tomcat-user@jakarta.apache.org X-EXP32-SerialNo: 00000323 Subject: org.apache.tomcat.security?? Message-ID: <38D62480@jc> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: ExpressIT! 2000 (Hydra) SMTP v3.51.05 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N I see reference in the documents to a facility in tomcat to enforce authentication and access - does this exist and, if so, how do I use it? Basically, I'd like to restrict my webserver to users who have a password, and I don't need anything fancy. ---------------- Dr. John Coonrod, Vice President, jc@thp.org The Hunger Project, 15 East 26th Street, NY, NY 10010 www.thp.org