From tomcat-user-return-126565-apmail-jakarta-tomcat-user-archive=jakarta.apache.org@jakarta.apache.org Thu May 12 14:02:19 2005 Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org Received: (qmail 58165 invoked from network); 12 May 2005 14:02:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 12 May 2005 14:02:19 -0000 Received: (qmail 64836 invoked by uid 500); 12 May 2005 14:05:23 -0000 Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 64745 invoked by uid 500); 12 May 2005 14:05:22 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: 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 64696 invoked by uid 99); 12 May 2005 14:05:21 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=HTML_50_60,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of Ankit_Shah@symantec.com designates 198.6.49.12 as permitted sender) Received: from navgwout.symantec.com (HELO navgwout.symantec.com) (198.6.49.12) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 12 May 2005 07:05:18 -0700 Received: from navgwout.symantec.com (localhost [127.0.0.1]) by navgwout.symantec.com (8.12.11/8.12.11) with SMTP id j4CDxhfp026106; Thu, 12 May 2005 07:01:13 -0700 (PDT) Received: from uscu-smtpob01-1.symantec.com ([155.64.74.130]) by navgwout.symantec.com (SMSSMTP 4.0.4.64) with SMTP id M2005051207011323194 ; Thu, 12 May 2005 07:01:13 -0700 Received: from uscu-smtpob01-1.symantec.com by uscu-smtpob01-1.symantec.com via smtpd (for navgwout.symantec.com [198.6.49.12]) with ESMTP; Thu, 12 May 2005 07:01:13 -0700 In-Reply-To: <1115861688.43962.ezmlm@jakarta.apache.org> To: markt@apache.org Cc: tomcat-user@jakarta.apache.org Subject: Re: tomcat-user Digest 12 May 2005 01:34:48 -0000 Issue 5616 MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5.1 January 21, 2004 From: Ankit Shah Message-ID: Date: Thu, 12 May 2005 10:01:07 -0400 X-MIMETrack: Serialize by Router on USCU-SMTPOB01-1/GLOBE-ADMIN/SYMANTEC(Release 6.5.1|January 21, 2004) at 05/12/2005 07:01:13 AM, Serialize complete at 05/12/2005 07:01:13 AM Content-Type: multipart/alternative; boundary="=_alternative 004D007B85256FFF_=" X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --=_alternative 004D007B85256FFF_= Content-Type: text/plain; charset="US-ASCII" Hi Mark, My jar file is placed in $CATALINA_HOME/server/lib/ Here is the slice of my server.xml Thanks, Ankit tomcat-user-digest-help@jakarta.apache.org 05/11/2005 09:34 PM Please respond to "Tomcat Users List" To tomcat-user@jakarta.apache.org cc Subject tomcat-user Digest 12 May 2005 01:34:48 -0000 Issue 5616 tomcat-user Digest 12 May 2005 01:34:48 -0000 Issue 5616 Topics (messages 126492 through 126521): Re: Issues with Custom Realm in Tomcat 5.5 126492 by: Mark Thomas ---------------------------------------------------------------------- ----- Message from Mark Thomas on Wed, 11 May 2005 19:08:15 +0100 ----- To: Tomcat Users List Subject: Re: Issues with Custom Realm in Tomcat 5.5 Where are you placing the .jar/.class files for your custom realm? At what level in server.xml is your realm configured? Mark Ankit Shah wrote: > Hi everyone, > I hope someone can help us with this problem. > > Current Tomcat settings: > Release in use: 5.5.9 along with 1.4.2 compatibility add-on > Logging using Log4J > JRE version: 1.4.2_05 > > We have written our own custom realm that essentially extends the standard > DataSource Realm. However, we are unable to authenticate users of Tomcat's > admin and manager application using our Realm. When setting Log4J logging > level to Debug, we discovered the following: > > 1. The Realm is loaded into the MBean Manager. We see a message 'MBean > successfully registered' for our Realm > 2. When admin is user is being validated, the log messages say > 'ClassLoader error: class not found'. and authentication fails. I am not > sure whether it failed to load our Realm (shouldn't happen since already > registered with MBean) or something else went missing. We CAN perform > authentication using the MemoryRealm that's configured by default. > > What makes this problem even more strange is our Realm worked successfully > with Tomcat 5.5.7 > > Anyone have ANY suggestions as where can we investigate for this problem, > please do respond back > > Thanks in advance. > > Ankit > --=_alternative 004D007B85256FFF_=--