Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org Received: (qmail 74557 invoked from network); 9 Apr 2005 01:26:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 9 Apr 2005 01:26:10 -0000 Received: (qmail 82567 invoked by uid 500); 9 Apr 2005 01:25:46 -0000 Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 82552 invoked by uid 500); 9 Apr 2005 01:25:46 -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 82537 invoked by uid 99); 9 Apr 2005 01:25:46 -0000 X-ASF-Spam-Status: No, hits=1.0 required=10.0 tests=DNS_FROM_RFC_ABUSE,RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS,URIBL_SBL X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of jerome.jar@gmail.com designates 64.233.170.197 as permitted sender) Received: from rproxy.gmail.com (HELO rproxy.gmail.com) (64.233.170.197) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 08 Apr 2005 18:25:44 -0700 Received: by rproxy.gmail.com with SMTP id j1so796542rnf for ; Fri, 08 Apr 2005 18:25:43 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=mPLCR6a9tIfqZer216lzzhuoOJUE0Th6jrcY8N5AEjtcpkgJRrAyT/peLyu/4odYqpuyp7HfOEsYjb/hTBwMu5/n6n8yGNgQpICoN+8VqQiUASQObnYUO7p9SG0TqBKJWC3mPXS33plGPk1pB+qItWXG7ZWgBaje7aW+sYtaGeo= Received: by 10.38.65.1 with SMTP id n1mr2324274rna; Fri, 08 Apr 2005 18:25:42 -0700 (PDT) Received: by 10.38.208.67 with HTTP; Fri, 8 Apr 2005 18:25:42 -0700 (PDT) Message-ID: <57fe892e0504081825459c8882@mail.gmail.com> Date: Sat, 9 Apr 2005 09:25:42 +0800 From: Jerome Jar Reply-To: Jerome Jar To: Tomcat Users List Subject: Re: Tomcat user 'roles' question In-Reply-To: <023201c53c62$27973650$28ad93d1@irm.local> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <023201c53c62$27973650$28ad93d1@irm.local> X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I think you can modify the "UserDatabase" part in server.xml, to change the authentiation to use in your own way. On Apr 9, 2005 1:41 AM, Wendy Smoak wrote: > The only exposure that I have to this is configuring tomcat-users.xml so I > can use the manager webapp, so please bear with me. > > I've got several web front-ends for a non-JDBC database. There is a 'green > screen' (telnet) app running against the DB that uses a system of user > security classes to which different 'screens' are assigned. That data is > stored in the DB itself. We've fit the web front end into this system by > assigning each 'page' of the webapp a 'screen id', so that the admin can > define who sees what in a single place. > > What I'm wondering is if there's any hope of using this data with the > existing request.isUserInRole() method. (The security classes are (loosely) > roles.) I only need to deal with authorization. Authentication is handled > separately by a Filter that redirects elsewhere to make them log in. > > Can someone point me in the right general direction? Everything Google > turns up starts in with configuring a JDBC or JNDI realm, and I don't think > that part of it will ever work with this database. Would I end up defining > my own kind of a Realm? > > Confused, > -- > Wendy Smoak > > --------------------------------------------------------------------- > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org