[jboss-jira] [JBoss JIRA] (WFLY-11892) With Elytron the legacy RunAsLoginModule no longer works

[Brian Loss (Jira)]

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

Brian Loss commented on WFLY-11892:
-----------------------------------

The legacy code I have _requires_ the use of the RunAsLoginModule since I need to call a secured EJB from the custom login module. Therefore, my legacy code is not supported even though your documentation indicates it should be.

> With Elytron the legacy RunAsLoginModule no longer works
> --------------------------------------------------------
>
>                 Key: WFLY-11892
>                 URL: https://issues.jboss.org/browse/WFLY-11892
>             Project: WildFly
>          Issue Type: Bug
>          Components: Security
>            Reporter: Brian Loss
>            Assignee: Ivo Studensky
>            Priority: Major
>
> When using the legacy jaas configuration, the RunAsLoginModule no longer works. While the module is invoked, there is no SecurityContext, so the login module cannot do any work and the temporary identity is never pushed on to the stack.
> It seems that previously, [this line|https://github.com/wildfly/wildfly/blob/16.0.0.Final/undertow/src/main/java/org/wildfly/extension/undertow/deployment/UndertowDeploymentInfoService.java#L975] was responsible for setting up the security context. However, that action is no longer executed.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)