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 On Tue, 27 May 2003 07:16:59 -0700 Spencer <[EMAIL PROTECTED]> wrote: > I wrote a custom login module which works terrifically in JBoss 3.0.3 > - > Tomcat 4.1.12. However when I moved it to JBoss 3.0.7 - Tomcat 4.1.24 > problems started arising. > > It's a simple security setup, where there's one role for all users > who > can authenticate against ldap. The custom login module, just > retrieves > the encrypted password from ldap, encrypts the password as provided > by > the j_password parameter, compares the two, and returns true or false > from the login() method. The custom login module extends > AbstractServerLoginModule. > > If you provided correct authentication, you're logged in, and > everything is okay. If you fail authenticate, it doesn't kick you > over > to the url listed under <form-error-page/> of the web.xml file, it > just > brings up a HTTP 403 error page: "Access to the specified resource > (Access to the requested resource has been denied) has been > forbidden." > > > I've tried searching in the forums (which have been unpostable the > past > 24 hours), and the mailing lists, but I seem to be the only one with > this issue. > > Any and all help will be much appreciated. > > TIA, > 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
