[
https://issues.apache.org/jira/browse/GERONIMO-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks closed GERONIMO-3965.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.2
2.1.x
2.0.x
I'm a bit embarassed to say that when I personally ran into this problem it
seemed more pressing and there was a fairly easy solution by using a delegating
login module that knows what classloader is required for the login module.
trunk rev 657967
branches/2.1 rev 657968
branches/2.0 rev 657969
> Custom LoginModule uses wrong classloader
> -----------------------------------------
>
> Key: GERONIMO-3965
> URL: https://issues.apache.org/jira/browse/GERONIMO-3965
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: security
> Affects Versions: 2.0.2, 2.1
> Environment: Windows XP, JDK 1.5
> Reporter: Kory Markevich
> Assignee: David Jencks
> Fix For: 2.0.x, 2.1.x, 2.2
>
>
> When specifying a custom LoginModule implementation in a
> geronimo-application.xml file, the class cannot be loaded if it is in the
> EAR. Debugging, the classloader being used belongs to OpenEJB rather than
> the one for the application. I have tried both versions 2.0.2 and 2.1.
> This bug was discovered and discussed in the mailing lists
> (http://www.nabble.com/Custom-LoginModule-classloading-issue-in-gernimo-2.0.2-td14404472s134.html)
> but I couldn't find any JIRA's for it. Note that the workaround discussed
> in the thread cannot be used in our application, though I tried it anyway and
> couldn't get it working.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
