[jboss-jira] [JBoss JIRA] (WFLY-5569) Module dependencies don't work correctly when JAAS login is used in deployments
[
https://issues.jboss.org/browse/WFLY-5569?page=com.atlassian.jira.plugin....
]
Darran Lofthouse resolved WFLY-5569.
------------------------------------
Fix Version/s: 10.1.0.Final
Resolution: Won't Fix
This is going to be superseded by Elytron at some point anyway, however as from my initial
assessment this is far from trivial to address so the application is required to take
responsibility for class loading if it is using the LoginContext directly.
Module dependencies don't work correctly when JAAS login is used
in deployments
-------------------------------------------------------------------------------
Key: WFLY-5569
URL: https://issues.jboss.org/browse/WFLY-5569
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Josef Cacek
Assignee: Darran Lofthouse
Fix For: 10.1.0.Final
When user wants to use direct JAAS login call from a deployment (e.g. servlet), (s)he
will experience problems when LoginModule is placed in custom AS module.
Login modules works correctly if they come from PicketBox, but new modules doesn't
work.
This issue is based on [this StackOverflow
question|http://stackoverflow.com/questions/33203277/wildfly-and-jaas-log...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)