problemas após configurar o security-domain do standalone

Olá, Após implementar o serviço de login do projeto casadocodigo-3 surgiu o seguinte erro:

05:03:55,243 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "casadocodigo-3.war" (runtime-name: "casadocodigo-3.war")
05:03:56,174 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."casadocodigo-3.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."casadocodigo-3.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "casadocodigo-3.war"
    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)
Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found
    at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:669)
    at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.getDefaultResourceAdapterName(MessageDrivenComponentDescriptionFactory.java:274)
    at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processMessageBeans(MessageDrivenComponentDescriptionFactory.java:154)
    at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processAnnotations(MessageDrivenComponentDescriptionFactory.java:81)
    at org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.processAnnotations(AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.java:57)
    at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.deploy(AbstractDeploymentUnitProcessor.java:76)
    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
    ... 5 more

05:03:56,176 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("full-replace-deployment") failed - address: ([]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"casadocodigo-3.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"casadocodigo-3.war\".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment \"casadocodigo-3.war\"
    Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found"}}
05:04:01,327 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "casadocodigo-3.war" with deployment "casadocodigo-3.war"
05:04:01,329 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report
WFLYCTL0186:   Services which failed to start:      service jboss.deployment.unit."casadocodigo-3.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."casadocodigo-3.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "casadocodigo-3.war"
      service jboss.deployment.unit."casadocodigo-3.war".PARSE

Já no pom.xml :

Failure to transfer org.sonatype.plexus:plexus-sec-dispatcher:jar:1.3 from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.sonatype.plexus:plexus-sec-dispatcher:jar:1.3 from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org

Obg.