[jboss-jira] [JBoss JIRA] (WFLY-9162) EEConcurrentManagementTestCase fails with security manager

James Perkins (JIRA) issues at jboss.org
Thu Aug 3 12:38:00 EDT 2017


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

James Perkins updated WFLY-9162:
--------------------------------
    Steps to Reproduce: 
cd wildfly/testsuite/integration/basic
mvn clean test   -Dtest=EEConcurrentManagementTestCase -Dsecurity.manager


  was:
cd wildfly/testsuite/domain
mvn clean test   -Dtest=EEConcurrentManagementTestCase -Dsecurity.manager




> EEConcurrentManagementTestCase fails with security manager
> ----------------------------------------------------------
>
>                 Key: WFLY-9162
>                 URL: https://issues.jboss.org/browse/WFLY-9162
>             Project: WildFly
>          Issue Type: Bug
>          Components: Test Suite
>            Reporter: Hynek Švábek
>
> EEConcurrentManagementTestCase fails with security manager
> {code}
> Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed:
>    JBOSS-LOCAL-USER: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.io.FilePermission" "/home/hsvabek/securityworkspace/VERIFICATION/2017_08_02_BEAP-7584/jboss-eap-7.1.0.ER3-src/testsuite/integration/basic/target/jbossas/standalone/tmp/auth/local55625406098549935.challenge" "read")" in code source "(vfs:/content/EEConcurrentManagementTestCase.jar <no signer certificates>)" of "ModuleClassLoader for Module "deployment.EEConcurrentManagementTestCase.jar" from Service Module Loader")
>    DIGEST-MD5: javax.security.sasl.SaslException: DIGEST-MD5: Server rejected authentication
>         at org.jboss.remoting3.remote.ClientConnectionOpenListener.allMechanismsFailed(ClientConnectionOpenListener.java:109)
>         at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:400)
>         at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242)
>         at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
>         at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
>         at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
>         at org.xnio.nio.WorkerThread.run(WorkerThread.java:571)
>         at ...asynchronous invocation...(Unknown Source)
>         at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:542)
>         at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:504)
>         at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:492)
>         at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:194)
>         at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:118)
>         ... 157 more
> ...
> {code}



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



More information about the jboss-jira mailing list