[JBoss JIRA] (AS7-3888) Loading custom login module from ear without the need for installing it as a jboss module
8:40 a.m.
Daniel Jipa created AS7-3888:
--------------------------------
Summary: 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: Anil Saldhana
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
9:02 a.m.
[
https://issues.jboss.org/browse/AS7-3888?page=com.atlassian.jira.plugin.s...
]
Anil Saldhana commented on AS7-3888:
------------------------------------
Please attach the ear file to this jira issue, for future reference.
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: Anil Saldhana
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
9:04 a.m.
[
https://issues.jboss.org/browse/AS7-3888?page=com.atlassian.jira.plugin.s...
]
Anil Saldhana updated AS7-3888:
-------------------------------
Attachment: myear.ear
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: Anil Saldhana
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
10:32 a.m.
[
https://issues.jboss.org/browse/AS7-3888?page=com.atlassian.jira.plugin.s...
]
Darran Lofthouse reassigned AS7-3888:
-------------------------------------
Assignee: Darran Lofthouse (was: Anil Saldhana)
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
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
10:36 a.m.
[
https://issues.jboss.org/browse/AS7-3888?page=com.atlassian.jira.plugin.s...
]
Darran Lofthouse updated AS7-3888:
----------------------------------
Fix Version/s: 7.1.1.Final
Need to review how these custom modules are accessed - within the ear may not make sense
too much as this is central server configuration then depending on a single deployment -
however the additional module approach may also be more than is desirable.
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
10:45 a.m.
[
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
3:58 p.m.
[
https://issues.jboss.org/browse/AS7-3888?page=com.atlassian.jira.plugin.s...
]
Jason Greene updated AS7-3888:
------------------------------
Fix Version/s: 7.1.2.Final
(was: 7.1.1.Final)
This issue is being relocated to 7.1.2 so that 7.1.1 only contains criticals, blockers,
and EAP LA issues (which are probably not yet at the right status, or need an extra triage
pass).
If these issues are completed in a 7.1.1 timeframe please change the fix version. Although
if you forget I will bulk correct.
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.2.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
9:22 a.m.
New subject: [JBoss JIRA] (AS7-3888) Deployment provided login modules for security domains are not accessible to remote invocation
[
https://issues.jboss.org/browse/AS7-3888?page=com.atlassian.jira.plugin.s...
]
Jason Greene updated AS7-3888:
------------------------------
Summary: Deployment provided login modules for security domains are not accessible to
remote invocation (was: Loading custom login module from ear without the need for
installing it as a jboss module)
Deployment provided login modules for security domains are not
accessible to remote invocation
----------------------------------------------------------------------------------------------
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.2.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
9:30 a.m.
New subject: [JBoss JIRA] (AS7-3888) Deployment provided login modules for security domains are not accessible to remote invocation
[
https://issues.jboss.org/browse/AS7-3888?page=com.atlassian.jira.plugin.s...
]
Jason Greene closed AS7-3888.
-----------------------------
Fix Version/s: No Release
(was: 7.1.2.Final)
Resolution: Rejected
This is by design (explanation to follow). Although instead of modifying the security
module, the best approach is to define a new static module with its own jar (placing it in
the modules dir) and reference it using the module="" tag in the security domain
login module stack.
The reason it is not possible to use application classes is that remoting connections
perform authentication once during the negotiation phase of the connection, and all
subsequent ejb (or jndi etc) invocations share the same connection. So an authenticated
connection can potentially span an arbitrary number of applications, and that information
can not be known at the time of authentication.
Deployment provided login modules for security domains are not
accessible to remote invocation
----------------------------------------------------------------------------------------------
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: No Release
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
12:27 p.m.
New subject: [JBoss JIRA] (AS7-3888) Deployment provided login modules for security domains are not accessible to remote invocation
[
https://issues.jboss.org/browse/AS7-3888?page=com.atlassian.jira.plugin.s...
]
Jason Greene commented on AS7-3888:
-----------------------------------
To help usability in this area we are going to attempt to include AS7-3905 soon
Deployment provided login modules for security domains are not
accessible to remote invocation
----------------------------------------------------------------------------------------------
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: No Release
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
4646
days inactive
4647
days old
9 comments
4 participants
participants (4)
-
Anil Saldhana (JIRA) -
Daniel Jipa (JIRA)
-
Darran Lofthouse (JIRA)
-
Jason Greene (JIRA)