Strange, cause I have been using the JAAS jars as provided under the JBoss distribution WITHOUT giving thought to whether it was a Sun implementation or not. So under JBoss-3.0.3 it was "jaas.jar", and under JBoss-3.0.7 it is "jboss-jaas.jar".
So it really doesn't explain why it didn't work before. It works now, so I guess I shouldn't complain. vvvvvvvvvvvvvvvvvvvvv No, what changed is that we quit patching the Sun supplied jaas.jar to work correctly with the thread context class loader when loading login modules. If you are using the Sun jaas.jar instead of the jboss-jaas.jar then you would have to use the ProxyLoginModule to load your login module. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Spencer" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, May 27, 2003 9:16 AM Subject: [JBoss-user] Re: Form-based security problems in JBoss 3.0.7 / Tomcat 4.1.12 > It seems that one of the changes from 3.0.3 to 3.0.7 was that the > AbstractServerLoginModule was removed from JBoss's class path. > > Using ProxyLoginModule with my custom login module worked like it was > supposed to. > > Spencer ------------------------------------------------------- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
