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

[Ivo Studensky (Jira)]

     [ https://issues.jboss.org/browse/WFLY-11892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivo Studensky resolved WFLY-11892.
----------------------------------
    Resolution: Rejected


Combination of legacy RunAsLoginModule and Elytron is considered unsupported. 

>From the Darran's email:
Once a deployment is making use of WildFly Elytron the login modules such as RunAsLoginModule which rely on the PicketBox security context would not be supported as that security context no longer exists.

The wrapping of the legacy security domains that we do provide with Elytron SecurityRealms is just so users can continue to use code they have implemented in the past to interact with their repository of identities.


> 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)