[jboss-jira] [JBoss JIRA] (WFLY-4043) Cannot load custom login module

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024586#comment-13024586 ] 

Brian Stansberry commented on WFLY-4043:
----------------------------------------

Have you asked about this on the forums? Setting up a security domain with a RealmDirect login-module and then having the security-realm use that JAAS security domain seems circular to me.

I understand why there could be an issue here -- the quickstart counts on the fact that LoginContext will use the TCCL to load the login module class, and when the EJB call is made, the TCCL is the deployment's classloader, so the class is visible. It doesn't surprise me that the deployment classloader is not the TCCL when other call patterns are used.

The basic solution to that would be to package the login module code in a module in the $WILDFLY_HOME/modules dir and use the "login-module" element's "module" attribute to specify the name of the module. But I'm not sure if you really want to package the login module class in the deployment, or if that's just something you're doing because the quickstart did it that way.

> Cannot load custom login module
> -------------------------------
>
>                 Key: WFLY-4043
>                 URL: https://issues.jboss.org/browse/WFLY-4043
>             Project: WildFly
>          Issue Type: Bug
>          Components: Security
>    Affects Versions: 8.1.0.Final
>         Environment: Java 1.8.0_25
>            Reporter: Rostyslav Smirnov
>            Assignee: Jason Greene
>
> When security realm authentication is configured to use JAAS domain, it is not possible to use custom login module, because there is no loader present for deployed classes. LoginContext attempts to load the login module class and fails with ClassNotFoundException.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)