This is a known issue with the JAAS 1.0.1 implementation. The
org.jboss.security.auth.spi.ProxyLoginModule can be used to
work around this issue:
/** A proxy LoginModule that loads a delegate LoginModule using
the current thread context class loader. The purpose of this
module is to work around the current JAAS class loader limitation
that requires LoginModules to be on the classpath. Some LoginModules
use core JBoss classes that would have to be moved into the jboss-jaas.jar
and packaging becomes a mess. Instead, these LoginModules are left
in the jbosssx.jar and the ProxyLoginModule is used to bootstrap
the non-classpath LoginModule.
@author [EMAIL PROTECTED]
@version $Revision: 1.1 $
*/
Sample auth.conf entry
proxy {
org.jboss.security.auth.spi.ProxyLoginModule required
moduleName="your.custom.login.Module"
option1="value1";
};
----- Original Message -----
From: "Ferguson, Doug" <[EMAIL PROTECTED]>
To: "JBoss User (E-mail)" <[EMAIL PROTECTED]>
Sent: Friday, June 15, 2001 2:23 PM
Subject: [JBoss-user] ClientLogin module can't load from tomcat context
> Hi,
>
> I am using integrated tomcat and my client login module will only load from
> a jar file that I explicitly put in my JBOSS_CLASSPATH....
>
> If it is in my WEB-INF/classes or my WEB-INF/lib it won't load.
>
> Is this a classloader problem?
>
> d.
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
