[jboss-jira] [JBoss JIRA] (WFLY-8322) EJB3 subsystem should not depend on legacy security subsystem

[Brian Stansberry (JIRA)]

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

Brian Stansberry moved JBEAP-9424 to WFLY-8322:
-----------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-8322  (was: JBEAP-9424)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: EJB
                       Security
                           (was: EJB)
                           (was: Security)
    Affects Version/s:     (was: 7.1.0.DR11)


> EJB3 subsystem should not depend on legacy security subsystem
> -------------------------------------------------------------
>
>                 Key: WFLY-8322
>                 URL: https://issues.jboss.org/browse/WFLY-8322
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB, Security
>            Reporter: Jan Martiska
>            Assignee: Brian Stansberry
>            Priority: Critical
>
> After removing the legacy {{security}} subsystem and booting the server, you see
> {noformat}
> 12:22:54,842 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "ejb3")]) - failure description: {
>     "WFLYCTL0412: Required services that are not installed:" => ["jboss.security.simple-security-manager"],
>     "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ejb.utilities is missing [jboss.security.simple-security-manager]"]
> }
> {noformat}
> Which means that EJB3 subsystem requires functionality of the legacy security subsystem.  It should be possible to completely get rid of the legacy subsystem and work with just Elytron.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)