Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <1109402555.1248673574891.JavaMail.jira@brutus>
Date: Sun, 26 Jul 2009 22:46:14 -0700 (PDT)
From: "David Jencks (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Closed: (GERONIMO-1602) Switching from Tomcat causes error
 in JAAS module: "Unable to instantiate login module"
In-Reply-To: <606156396.1139401020225.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/GERONIMO-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jencks closed GERONIMO-1602.
----------------------------------

    Resolution: Cannot Reproduce

I think the code and classloaders surrounding this problem have changed enough so that the report is no longer relvant.  No one seems to have complained about similar problems recently.  

> Switching from Tomcat causes error in JAAS module: "Unable to instantiate login module"
> ---------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-1602
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-1602
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: security, Tomcat
>    Affects Versions: 1.0
>         Environment: Windows XP Prof, JDK 1.5.0_06, Geronimo 1.0 (Tomcat, .zip)
>            Reporter: Karsten Voges
>             Fix For: 1.1.x
>
>         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 catalina.properties I set
> #######JAAS
> java.security.auth.login.config=${catalina.base}/conf/login.config
> and the login.config looks like this:
> MyApp {
>     de.jato.security.auth.module.JatoServletLoginModule 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:
> javax.security.auth.login.LoginException: org.apache.geronimo.common.GeronimoSecurityException: Unable to instantiate login module
> Caused by: java.lang.ClassNotFoundException: de.jato.security.auth.module.JatoServletLoginModule
> 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.
-
You can reply to this email to add a comment to the issue online.