[jboss-jira] [JBoss JIRA] (AS7-5556) Authentication failure of AS instance connecting to host controller with different file.encoding

[Darran Lofthouse (JIRA)]

Darran Lofthouse created AS7-5556:
-------------------------------------

             Summary: Authentication failure of AS instance connecting to host controller with different file.encoding
                 Key: AS7-5556
                 URL: https://issues.jboss.org/browse/AS7-5556
             Project: Application Server 7
          Issue Type: Bug
          Components: Domain Management, Security
    Affects Versions: 7.1.2.Final (EAP)
            Reporter: Darran Lofthouse
            Assignee: Darran Lofthouse
             Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP)


If a server group is updated to say the following: -

{code}

        <server-group name="main-server-group" profile="full">
            <jvm name="default">
                <heap size="64m" max-size="512m"/>
            </jvm>
            <socket-binding-group ref="full-sockets"/>
            <system-properties>
               <property name="file.encoding" value="ISO8859_1" boot-time="true"/>
            </system-properties>             
        </server-group>
{code}

Then when server within this server group attempt to connect back to their host controller the following is logged: -

{code}

[Server:server-one] 15:11:02,069 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: java.util.concurrent.ExecutionException: Operation failed
[Server:server-one] 	at org.jboss.as.server.ServerStartTask$2$1.load(ServerStartTask.java:179) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Server:server-one] 	at org.jboss.as.server.ServerService.boot(ServerService.java:292) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Server:server-one] 	at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:156) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Server:server-one] 	at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_32]
[Server:server-one] Caused by: java.util.concurrent.ExecutionException: Operation failed
[Server:server-one] 	at org.jboss.threads.AsyncFutureTask.operationFailed(AsyncFutureTask.java:74) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]
[Server:server-one] 	at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:268) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]
[Server:server-one] 	at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$2.get(ServerBootOperationsService.java:107) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Server:server-one] 	at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$2.get(ServerBootOperationsService.java:89) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Server:server-one] 	at org.jboss.as.server.ServerStartTask$2$1.load(ServerStartTask.java:176) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Server:server-one] 	... 3 more
[Server:server-one] Caused by: java.net.ConnectException: JBAS012174: Could not connect to remote://127.0.0.1:9999. The connection failed
[Server:server-one] 	at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:118) [jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Server:server-one] 	at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:247) [jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Server:server-one] 	at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) [jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Server:server-one] 	at org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:105) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Server:server-one] 	at org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:81) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Server:server-one] 	at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:69) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Server:server-one] 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_32]
[Server:server-one] 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_32]
[Server:server-one] 	at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_32]
[Server:server-one] 	at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]
[Server:server-one] Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
[Server:server-one] 	at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:327) [jboss-remoting-3.2.8.SP1.jar:3.2.8.SP1]
[Server:server-one] 	at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:226) [jboss-remoting-3.2.8.SP1.jar:3.2.8.SP1]
[Server:server-one] 	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) [xnio-api-3.0.6.GA.jar:3.0.6.GA]
[Server:server-one] 	at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) [xnio-api-3.0.6.GA.jar:3.0.6.GA]
[Server:server-one] 	at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) [xnio-api-3.0.6.GA.jar:3.0.6.GA]
[Server:server-one] 	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) [xnio-api-3.0.6.GA.jar:3.0.6.GA]
[Server:server-one] 	at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) [xnio-api-3.0.6.GA.jar:3.0.6.GA]
[Server:server-one] 	at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:180) [xnio-api-3.0.6.GA.jar:3.0.6.GA]
[Server:server-one] 	at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) [xnio-api-3.0.6.GA.jar:3.0.6.GA]
[Server:server-one] 	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) [xnio-api-3.0.6.GA.jar:3.0.6.GA]
[Server:server-one] 	at org.xnio.nio.NioHandle.run(NioHandle.java:90)
[Server:server-one] 	at org.xnio.nio.WorkerThread.run(WorkerThread.java:187)
[Server:server-one] 	at ...asynchronous invocation...(Unknown Source)
[Server:server-one] 	at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270) [jboss-remoting-3.2.8.SP1.jar:3.2.8.SP1]
[Server:server-one] 	at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251) [jboss-remoting-3.2.8.SP1.jar:3.2.8.SP1]
[Server:server-one] 	at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349) [jboss-remoting-3.2.8.SP1.jar:3.2.8.SP1]
[Server:server-one] 	at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:337) [jboss-remoting-3.2.8.SP1.jar:3.2.8.SP1]
[Server:server-one] 	at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:74) [jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Server:server-one] 	at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:88) [jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
[Server:server-one] 	... 9 more
{code}

A network trace of the communication between the AS instance and it's host controller shows that it is the Digest authentication that is failing and being rejected.

This is most likely one of the following causes: -
 1 - The individual password for the AS is passed to it as the process starts - the change in file.encoding could be affecting how this password is read.
 2 - A couple of digests are created based on this password, one or both of these could be wrong due to the new encoding - the message itself still claims utf-8.



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira