[jbossws-issues] [JBoss JIRA] Created: (JBWS-1820) Using JRE from vendors other than Sun the Remoting key store and trust store algorithms are not propagated

[Magesh Kumar B (JIRA)]

Using JRE from vendors other than Sun the Remoting key store and trust store algorithms are not propagated
----------------------------------------------------------------------------------------------------------

                 Key: JBWS-1820
                 URL: http://jira.jboss.com/jira/browse/JBWS-1820
             Project: JBoss Web Services
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
    Affects Versions: jbossws-1.0.4
         Environment: IBM JRE 1.5
JBoss4.0.4.GA with JBossWS1.0.4
            Reporter: Magesh Kumar B


When we use JVMs other than Sun the Remoting properties are not reset from the default. For e.g., using IBM JRE and https SE URL the following exception is thrown. Currently there is no way to set the Remoting SSL Socket Factory parameter REMOTING_ALGORITHM or REMOTING_TRUST_ALGORITHM

java.lang.RuntimeException: java.io.IOException: Error creating Remoting SSL Socket Factory:SunX509 KeyManagerFactory not available
	at org.jboss.remoting.util.socket.RemotingSSLSocketFactory.getSupportedCipherSuites(RemotingSSLSocketFactory.java:657)
	at com.ibm.jsse2.ExportControl.checkCipherSuites(ExportControl.java:10)
	at com.ibm.net.ssl.www2.protocol.https.b.afterConnect(b.java:3)
	at com.ibm.net.ssl.www2.protocol.https.c.connect(c.java:62)
	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:866)
	at com.ibm.net.ssl.www2.protocol.https.a.getOutputStream(a.java:25)
	at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:163)
	at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:81)
	at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)
	at org.jboss.remoting.Client.invoke(Client.java:525)
	at org.jboss.remoting.Client.invoke(Client.java:488)
	at org.jboss.ws.soap.SOAPConnectionImpl.call(SOAPConnectionImpl.java:185)
	at org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:689)
	at org.jboss.ws.jaxrpc.CallImpl.invoke(CallImpl.java:398)
	at org.jboss.ws.jaxrpc.CallProxy.invoke(CallProxy.java:164)
	at $Proxy57.vmsdkGetBrowseInfoFromHost(Unknown Source)
                     .................
Caused by: 
java.io.IOException: Error creating Remoting SSL Socket Factory:SunX509 KeyManagerFactory not available
	at sun.security.jca.GetInstance.getInstance(GetInstance.java:158)
	at javax.net.ssl.KeyManagerFactory.getInstance(KeyManagerFactory.java:20)
	at org.jboss.remoting.util.socket.RemotingSSLSocketFactory.loadKeyManagers(RemotingSSLSocketFactory.java:288)
	at org.jboss.remoting.util.socket.RemotingSSLSocketFactory.init(RemotingSSLSocketFactory.java:177)
	at org.jboss.remoting.util.socket.RemotingSSLSocketFactory.getSupportedCipherSuites(RemotingSSLSocketFactory.java:653)
	... 65 more

Please allow this and other properties to be set in SOAPConnectionImpl.java and CallProxy.java

In newer Remoting version we have more properties that can make a difference:

REMOTING_KEY_ALIAS
REMOTING_CLIENT_AUTH_MODE
REMOTING_SERVER_AUTH_MODE
REMOTING_SSL_PROTOCOL
REMOTING_SSL_PROVIDER_NAME
REMOTING_SERVER_SOCKET_USE_CLIENT_MODE
REMOTING_SOCKET_USE_CLIENT_MODE

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira