geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Commented: (GERONIMO-1602) Switching from Tomcat causes error in JAAS module: "Unable to instantiate login module"
Date Wed, 08 Feb 2006 13:02:57 GMT
    [ ] 

David Jencks commented on GERONIMO-1602:

This is a known problem, that gbeans in a web plan cannot use the classes in the war, and
in fact the war classes are not in the configuration classloader.  The only solution at the
moment is to move or copy the classes to a jar outside the war and use a dependency element
to that jar in the plan that contains the login gbeans.

We might be able to solve this problem in the 1.1 release but the code is not yet written.


> Switching from Tomcat causes error in JAAS module: "Unable to instantiate login module"
> ---------------------------------------------------------------------------------------
>          Key: GERONIMO-1602
>          URL:
>      Project: Geronimo
>         Type: Bug
>   Components: security, Tomcat
>     Versions: 1.0
>  Environment: Windows XP Prof, JDK 1.5.0_06, Geronimo 1.0 (Tomcat, .zip)
>     Reporter: Karsten Voges
>  Attachments: geronimo-JAAS-login-error.txt
> I have a problem with porting a Tomcat application to Geronimo. The error stacktrace
is attached.
> I deployed the war without any deployment plan and the app seams to be working (JSPs
work and the startup-servlet works as well)
> But the JAASLoginModule was missing, so I could not log in. -> so far no Problem!
> Afterwards I configured a security realm with the console and after a restart my app
does not complain about a missing LoginModule but throws the attached error stacktrace.
> For Tomcat I do the following:
> in I set
> #######JAAS
> and the login.config looks like this:
> MyApp {
> Sufficient loginServlet="/login/login.jsp";
> };
> I tried to use a special geronimo-web.xml where I set the
> <context-priority-classloader>true</context-priority-classloader>
> But I still get the same error:
> org.apache.geronimo.common.GeronimoSecurityException:
Unable to instantiate login module
> Caused by: java.lang.ClassNotFoundException:
> Am I doing something wrong? The class is in the war I deployed, and everything works
fine in Tomcat.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message