[jboss-jira] [JBoss JIRA] (AS7-3888) Loading custom login module from ear without the need for installing it as a jboss module
[
https://issues.jboss.org/browse/AS7-3888?page=com.atlassian.jira.plugin.s...
]
Anil Saldhana commented on AS7-3888:
------------------------------------
When the user had a custom login module in a separate module and in the login module
configuration, they specify the module attribute to indicate the JBoss Module where it is
located, then we install
https://github.com/anilsaldhana/jboss-as/blob/master/security/src/main/ja...
to deal with the tccl/modulecl issue when JDK jaas kicks off. In the case of custom
login module sitting in the application class path (war, ejb jar) etc, it is available on
the tccl for the JDK. I am unsure why in this particular ear case, the tccl does not have
it.
Loading custom login module from ear without the need for installing
it as a jboss module
-----------------------------------------------------------------------------------------
Key: AS7-3888
URL: https://issues.jboss.org/browse/AS7-3888
Project: Application Server 7
Issue Type: Enhancement
Components: Security
Affects Versions: 7.1.0.Final
Environment: Reproduced on Ubuntu 10.04.3 LTS, CentOS release 5.7, Windows 7
Reporter: Daniel Jipa
Assignee: Darran Lofthouse
Fix For: 7.1.1.Final
Attachments: myear.ear
When using a remote jndi connection to AS and a custom security-realm for it that is tied
to a custom login module the authentication only works when packaging the class in a jar
and installing it on jboss_install_dir/modules/org/jboss/as/remoting/main. It should be
loadable from ear also.
More details here: https://community.jboss.org/thread/195501
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira