[ https://issues.jboss.org/browse/WFLY-12464?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12464: ------------------------------------ Description: The CLI script that sets up the config used in testsuite/integration/elytron leaves an empty shell legacy security subsystem around, saying: {code} # datasources and ejb3 still has dependency on legacy security subsystem, so we can't remove it completely now {code} But actually removing it, the tests all pass but two. And one of those fails simply because it includes a setup task management up to disable JACC in the legacy subsystem, which would not be necessary if it were not present. The other failure I believe is due to a flaw in the Elytron subsystem that will be fixed by WFCORE-4640. Basically in the absence of the legacy subsystem no DUP adds JASPI or JACC dependencies to the deployment module. was: The CLI script that sets up the config used in testsuite/integration/elytron leaves an empty shell legacy security subsystem around, saying: # datasources and ejb3 still has dependency on legacy security subsystem, so we can't remove it completely now But actually removing it, the tests all pass but two. And one of those fails simply because it includes a setup task management up to disable JACC in the legacy subsystem, which would not be necessary if it were not present. The other failure I believe is due to a flaw in the Elytron subsystem that will be fixed by WFCORE-4640. Basically in the absence of the legacy subsystem no DUP adds JASPI or JACC dependencies to the deployment module. -- This message was sent by Atlassian Jira (v7.13.5#713005)