[jboss-jira] [JBoss JIRA] (WFLY-3831) Securing EJB comunitication via SSL is failed
Jonhny Jonhny (JIRA)
issues at jboss.org
Tue Sep 9 06:47:00 EDT 2014
[ https://issues.jboss.org/browse/WFLY-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonhny Jonhny updated WFLY-3831:
--------------------------------
Description:
I added the SSL configuration for ApplicationRealm as the guide in Jboss document, but It's failed when trying connection to server (Note that if I remove SSL configuration, it can connect to server successfully)
<management>
<security-realms>
<security-realm name="ManagementRealm">
<authentication>
<local default-user="$local"/>
<properties path="mgmt-users.properties" relative-to="jboss.server.config.dir"/>
</authentication>
</security-realm>
<security-realm name="ApplicationRealm">
<server-identities>
<ssl>
<keystore path="server.keystore" relative-to="jboss.server.config.dir" keystore-password="ybxiang_keystore_password"/>
</ssl>
</server-identities>
<authentication>
<jaas name="ybxiang-forum-jaas-security-domain"/>
</authentication>
</security-realm>
</security-realms>
<management-interfaces>
<native-interface security-realm="ManagementRealm">
<socket-binding native="management-native"/>
</native-interface>
<http-interface security-realm="ManagementRealm">
<socket-binding http="management-http"/>
</http-interface>
</management-interfaces>
</management>
Client log
!ENTRY com 0 0 2014-09-09 15:52:05.124
!MESSAGE (Timezone is ICT.) ;3556; com.model.connection.ServerLink logged : "could not connect:
java.lang.RuntimeException: java.lang.RuntimeException: javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://172.41.211.111:4447]
at com.RemoteJMXDispatcher.connectToJMS(RemoteJMXDispatcher.java:455)
at com.RemoteJMXDispatcher.<init>(RemoteJMXDispatcher.java:295)
at com.RemoteJMXDispatcher.<init>(RemoteJMXDispatcher.java:288)
at com.model.connection.SecuredRemoteJMXDispatcher.<init>(SecuredRemoteJMXDispatcher.java:39)
at com.model.connection.SecuredRemoteJMXDispatcher.create(SecuredRemoteJMXDispatcher.java:86)
at com.model.connection.ServerLink.login(ServerLink.java:325)
at com.login.ConnectToServerRunnable.run(ConnectToServerRunnable.java:60)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: java.lang.RuntimeException: javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://192.168.95.111:4447]
at com.JMSUtil.getRemoteConnectionFactory(JMSUtil.java:108)
at com.JMSUtil.createRemoteConnection(JMSUtil.java:78)
at com.RemoteJMXDispatcher.connectToJMS(RemoteJMXDispatcher.java:404)
... 7 more
Caused by: javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://172.41.211.111:4447]
at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:213)
at org.jboss.naming.remote.client.HaRemoteNamingStore.namingStore(HaRemoteNamingStore.java:144)
at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:125)
at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:241)
at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:79)
at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:83)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at com.JMSUtil.getRemoteConnectionFactory(JMSUtil.java:101)
... 9 more"
Server log
2014-09-09 15:59:42,758 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:00:42,762 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:01:42,766 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:02:42,770 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:03:42,773 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:04:42,777 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:05:42,781 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
was:
I added the SSL configuration for ApplicationRealm as the guide in Jboss document, but It's failed when trying connection to server:
<management>
<security-realms>
<security-realm name="ManagementRealm">
<authentication>
<local default-user="$local"/>
<properties path="mgmt-users.properties" relative-to="jboss.server.config.dir"/>
</authentication>
</security-realm>
<security-realm name="ApplicationRealm">
<server-identities>
<ssl>
<keystore path="server.keystore" relative-to="jboss.server.config.dir" keystore-password="ybxiang_keystore_password"/>
</ssl>
</server-identities>
<authentication>
<jaas name="ybxiang-forum-jaas-security-domain"/>
</authentication>
</security-realm>
</security-realms>
<management-interfaces>
<native-interface security-realm="ManagementRealm">
<socket-binding native="management-native"/>
</native-interface>
<http-interface security-realm="ManagementRealm">
<socket-binding http="management-http"/>
</http-interface>
</management-interfaces>
</management>
Client log
!ENTRY com 0 0 2014-09-09 15:52:05.124
!MESSAGE (Timezone is ICT.) ;3556; com.model.connection.ServerLink logged : "could not connect:
java.lang.RuntimeException: java.lang.RuntimeException: javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://172.41.211.111:4447]
at com.RemoteJMXDispatcher.connectToJMS(RemoteJMXDispatcher.java:455)
at com.RemoteJMXDispatcher.<init>(RemoteJMXDispatcher.java:295)
at com.RemoteJMXDispatcher.<init>(RemoteJMXDispatcher.java:288)
at com.model.connection.SecuredRemoteJMXDispatcher.<init>(SecuredRemoteJMXDispatcher.java:39)
at com.model.connection.SecuredRemoteJMXDispatcher.create(SecuredRemoteJMXDispatcher.java:86)
at com.model.connection.ServerLink.login(ServerLink.java:325)
at com.login.ConnectToServerRunnable.run(ConnectToServerRunnable.java:60)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: java.lang.RuntimeException: javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://192.168.95.111:4447]
at com.JMSUtil.getRemoteConnectionFactory(JMSUtil.java:108)
at com.JMSUtil.createRemoteConnection(JMSUtil.java:78)
at com.RemoteJMXDispatcher.connectToJMS(RemoteJMXDispatcher.java:404)
... 7 more
Caused by: javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://172.41.211.111:4447]
at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:213)
at org.jboss.naming.remote.client.HaRemoteNamingStore.namingStore(HaRemoteNamingStore.java:144)
at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:125)
at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:241)
at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:79)
at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:83)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at com.JMSUtil.getRemoteConnectionFactory(JMSUtil.java:101)
... 9 more"
Server log
2014-09-09 15:59:42,758 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:00:42,762 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:01:42,766 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:02:42,770 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:03:42,773 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:04:42,777 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:05:42,781 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
> Securing EJB comunitication via SSL is failed
> ----------------------------------------------
>
> Key: WFLY-3831
> URL: https://issues.jboss.org/browse/WFLY-3831
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: JBoss AS7 7.2.0.Final
> Reporter: Jonhny Jonhny
> Assignee: David Lloyd
>
> I added the SSL configuration for ApplicationRealm as the guide in Jboss document, but It's failed when trying connection to server (Note that if I remove SSL configuration, it can connect to server successfully)
> <management>
> <security-realms>
> <security-realm name="ManagementRealm">
> <authentication>
> <local default-user="$local"/>
> <properties path="mgmt-users.properties" relative-to="jboss.server.config.dir"/>
> </authentication>
> </security-realm>
> <security-realm name="ApplicationRealm">
> <server-identities>
> <ssl>
> <keystore path="server.keystore" relative-to="jboss.server.config.dir" keystore-password="ybxiang_keystore_password"/>
> </ssl>
> </server-identities>
> <authentication>
> <jaas name="ybxiang-forum-jaas-security-domain"/>
> </authentication>
> </security-realm>
> </security-realms>
> <management-interfaces>
> <native-interface security-realm="ManagementRealm">
> <socket-binding native="management-native"/>
> </native-interface>
> <http-interface security-realm="ManagementRealm">
> <socket-binding http="management-http"/>
> </http-interface>
> </management-interfaces>
> </management>
> Client log
> !ENTRY com 0 0 2014-09-09 15:52:05.124
> !MESSAGE (Timezone is ICT.) ;3556; com.model.connection.ServerLink logged : "could not connect:
> java.lang.RuntimeException: java.lang.RuntimeException: javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://172.41.211.111:4447]
> at com.RemoteJMXDispatcher.connectToJMS(RemoteJMXDispatcher.java:455)
> at com.RemoteJMXDispatcher.<init>(RemoteJMXDispatcher.java:295)
> at com.RemoteJMXDispatcher.<init>(RemoteJMXDispatcher.java:288)
> at com.model.connection.SecuredRemoteJMXDispatcher.<init>(SecuredRemoteJMXDispatcher.java:39)
> at com.model.connection.SecuredRemoteJMXDispatcher.create(SecuredRemoteJMXDispatcher.java:86)
> at com.model.connection.ServerLink.login(ServerLink.java:325)
> at com.login.ConnectToServerRunnable.run(ConnectToServerRunnable.java:60)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> Caused by: java.lang.RuntimeException: javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://192.168.95.111:4447]
> at com.JMSUtil.getRemoteConnectionFactory(JMSUtil.java:108)
> at com.JMSUtil.createRemoteConnection(JMSUtil.java:78)
> at com.RemoteJMXDispatcher.connectToJMS(RemoteJMXDispatcher.java:404)
> ... 7 more
> Caused by: javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://172.41.211.111:4447]
> at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:213)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.namingStore(HaRemoteNamingStore.java:144)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:125)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:241)
> at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:79)
> at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:83)
> at javax.naming.InitialContext.lookup(InitialContext.java:411)
> at com.JMSUtil.getRemoteConnectionFactory(JMSUtil.java:101)
> ... 9 more"
>
>
> Server log
> 2014-09-09 15:59:42,758 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
> 2014-09-09 16:00:42,762 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
> 2014-09-09 16:01:42,766 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
> 2014-09-09 16:02:42,770 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
> 2014-09-09 16:03:42,773 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
> 2014-09-09 16:04:42,777 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
> 2014-09-09 16:05:42,781 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
More information about the jboss-jira
mailing list