Today, I applied for a new Aliyun server and installed jboss in the operation room. When I was happily deploying the project, I found the following problems were reported. A search on the Internet says that it is a user with no available permissions. When I was using it, I created a manage user and an application user (refer to the previous for the specific new method) to send messages to the jboss message queue. As a result, I looked at the configuration file, application-user under the standalone/configuration folder. .properties and application-role.properties and mgmt-user.properties files, there are no new users and roles in the three files. However , the corresponding file user under domain / configuration has been successfully added, which is very surprising (may be caused by the operation room renaming the standalone folder to server1, this will be verified later). The error is as follows:
"config-based-naming-client-endpoint" read-1) JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
14:23:43,753 ERROR [stderr] (Thread-81) javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.RuntimeException: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed]14:23:43,754 ERROR [stderr] (Thread-81) at org.jboss.naming.remote.client.ClientUtil.namingException(ClientUtil.java:36)
14:23:43,755 ERROR [stderr] (Thread-81) at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:121)
14:23:43,755 ERROR [stderr] (Thread-81) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
14:23:43,756 ERROR [stderr] (Thread-81) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
14:23:43,756 ERROR [stderr] (Thread-81) at javax.naming.InitialContext.init(InitialContext.java:223)
14:23:43,756 ERROR [stderr] (Thread-81) at javax.naming.InitialContext.<init>(InitialContext.java:197)
14:23:43,766 ERROR [stderr] (Thread-81) Caused by: java.lang.RuntimeException: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
14:23:43,769 ERROR [stderr] (Thread-81) at org.jboss.naming.remote.protocol.IoFutureHelper.get(IoFutureHelper.java:87)
14:23:43,769 ERROR [stderr] (Thread-81) at org.jboss.naming.remote.client.NamingStoreCache.getRemoteNamingStore(NamingStoreCache.java:56)
14:23:43,770 ERROR [stderr] (Thread-81) at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateCachedNamingStore(InitialContextFactory.java:166)
14:23:43,770 ERROR [stderr] (Thread-81) at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:139)
14:23:43,771 ERROR [stderr] (Thread-81) at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:104)
14:23:43,771 ERROR [org.jboss.remoting.remote.connection] (Remoting "config-based-naming-client-endpoint" read-1) JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
14:23:43,771 ERROR [stderr] (Thread-81) ... 8 more
14:23:43,775 ERROR [stderr] (Thread-81) Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
14:23:43,776 ERROR [stderr] (Thread-81) at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:365)
14:23:43,776 ERROR [stderr] (Thread-81) at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:214)
14:23:43,777 ERROR [stderr] (Thread-81) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
14:23:43,777 ERROR [stderr] (Thread-81) at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
14:23:43,778 ERROR [stderr] (Thread-81) at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
14:23:43,778 ERROR [stderr] (Thread-81) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
14:23:43,778 ERROR [stderr] (Thread-81) at org.xnio.nio.NioHandle.run(NioHandle.java:90)
14:23:43,779 ERROR [stderr] (Thread-81) at org.xnio.nio.WorkerThread.run(WorkerThread.java:184)
14:23:43,779 ERROR [stderr] (Thread-81) at ...asynchronous invocation...(Unknown Source)
14:23:43,779 ERROR [stderr] (Thread-81) at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270)
14:23:43,780 ERROR [stderr] (Thread-81) at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
14:23:43,780 ERROR [stderr] (Thread-81) at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
14:23:43,780 ERROR [stderr] (Thread-81) at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
14:23:43,781 ERROR [stderr] (Thread-81) at org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.connect(EndpointCache.java:105)
14:23:43,781 ERROR [stderr] (Thread-81) at org.jboss.naming.remote.client.NamingStoreCache.getRemoteNamingStore(NamingStoreCache.java:55)
14:23:43,782 ERROR [stderr] (Thread-81) ... 11 more
The solution is to copy the encrypted information in the corresponding file in the domain to the standalone configuration file (only copy the new content) and restart the service.