geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-3965) Custom LoginModule uses wrong classloader
Date Thu, 17 Apr 2008 22:21:21 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590225#action_12590225
] 

David Jencks commented on GERONIMO-3965:
----------------------------------------

Contrary to the comments on the mailing list thread, this isn't an openejb problem.  Login
modules are global resources and we need to set a thread context classloader suitable for
a realm before trying to use it.  Kinda messy.... but we didn't write the jaas spec.  Openejb
doesn't know which app you might be interested in at the point it is trying to authenticate
you here, so it wouldn't know what to do anyway.

I'd like to know what problems you found with the configuration suggestion I made in the thread.
 The user list would be a good place to discuss that.

> 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
>
> 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.


Mime
View raw message