A class can decide to only load classes from the system classpath
by using the ClassLoader.getSystemClassLoader(). This is what
JAAS 1.0 does and Rickard queried the JAAS security team early
on about this. They said they chose to be overly cautious about where
login modules were loaded from and required that login modules be loaded
from the system classpath. This has changed in the JAAS released as part
of 1.4, but for the current JAAS 1.0 release you either need to place login
modules and the classes they reference in the system classpath or use
the ProxyLogin module to work around this restriction.
----- Original Message -----
From: marc fleury
To: [EMAIL PROTECTED]
Sent: Saturday, August 04, 2001 5:28 PM
Subject: RE: [JBoss-user] JAAS requires staticly loaded classes?
|> it doesn't use the context classloader? only the system?
|
|Yes. That's how I remember it. Supposed to be fixed some time but
|from the sound of Doug's description, haven't been fixed yet.
but... but... whatever cl was used to load the jaas stuff is the cl that is
going to be asked **by the VM** to load the classes. it's not up to JAAS to
decide what CL to use, afaik, it is a VM decision. Or can you change that
behavior?
If that CL is the MLet one (as should be with MBean stuff) then those
classes are seen.
ah, another day, work to do...
marcf
|
|-- Juha
|
|
|
|
|_______________________________________________
|JBoss-user mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
