Hi Mark,
My jar file is placed in $CATALINA_HOME/server/lib/
Here is the slice of my server.xml
<Service name="Service-name">
<Engine defaultHost="localhost" name="Catalina">
<Realm className="my.realm.classname"
datasource="datasourcename" ... other attributes/>
<Host docbase="webapps" name="localhost"/>
</Engine>
</Service>
Thanks,
Ankit
[EMAIL PROTECTED]
05/11/2005 09:34 PM
Please respond to
"Tomcat Users List" <[EMAIL PROTECTED]>
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 <[EMAIL PROTECTED]> on Wed, 11 May 2005
19:08:15 +0100 -----
To:
Tomcat Users List <tomcat-user@jakarta.apache.org>
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
>
