[jboss-jira] [JBoss JIRA] (WFLY-5569) Module dependencies don't work correctly when JAAS login is used in deployments
Eduardo Silva (JIRA)
issues at jboss.org
Wed Feb 3 16:51:00 EST 2016
[ https://issues.jboss.org/browse/WFLY-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158521#comment-13158521 ]
Eduardo Silva commented on WFLY-5569:
-------------------------------------
With Elytron replacing JAAS as the integration point with the backing store of identities, this will still being relevant?
> 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
>
> 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-login-module]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list