-
1. Re: Can't connect to https webservices from my deployed .war. Please help!!!
msteedle Jul 25, 2011 2:29 PM (in response to msteedle)Can anybody help?
-
2. Re: Can't connect to https webservices from my deployed .war. Please help!!!
msteedle Jul 28, 2011 10:11 AM (in response to msteedle)?
-
3. Re: Can't connect to https webservices from my deployed .war. Please help!!!
jaikiran Jul 28, 2011 11:28 AM (in response to msteedle)Have you configured the https connector? What does the connector configuration look like and what does the code which calls the URL look like?
-
4. Re: Can't connect to https webservices from my deployed .war. Please help!!!
msteedle Jul 28, 2011 11:54 AM (in response to jaikiran)My configuration looks as follows:
<connector name="https" protocol="HTTP/1.1" socket-binding="https" scheme="https" secure="true">
<ssl name="https" key-alias="serverkeys" password="123456" certificate-key-file="C:/jboss-as-web-7.0.0.Final/standalone/configuration/server1.keystore"/>
</connector>
A snippet of the relevent code is:
String wsdlURL = "https://www.paypalobjects.com/wsdl/PayPalSvc.wsdl";
WsdlProject project = new WsdlProject();
WsdlInterface iface = WsdlInterfaceFactory.importWsdl(project,wsdlURL,true)[0];
Like I said, the code works fine running it from command prompt or eclipse, just not when its deployed using jboss.
-
5. Re: Can't connect to https webservices from my deployed .war. Please help!!!
msteedle Jul 28, 2011 11:56 AM (in response to msteedle)the corresponding binding socket is:
<socket-binding-group name="standard-sockets" default-interface="public">
<socket-binding name="http" port="8080"/>
<socket-binding name="https" port="8443"/>
<socket-binding name="jmx-connector-registry" port="1090"/>
<socket-binding name="jmx-connector-server" port="1091"/>
<socket-binding name="jndi" port="1099"/>
<socket-binding name="osgi-http" port="8090"/>
<socket-binding name="remoting" port="4447"/>
<socket-binding name="txn-recovery-environment" port="4712"/>
<socket-binding name="txn-status-manager" port="4713"/>
</socket-binding-group>
-
6. Re: Can't connect to https webservices from my deployed .war. Please help!!!
jaikiran Jul 28, 2011 12:00 PM (in response to msteedle)Matt Steedle wrote:
A snippet of the relevent code is:
String wsdlURL = "https://www.paypalobjects.com/wsdl/PayPalSvc.wsdl";
The https port in that configuration you posted is 8443. So the URL should have that port number.
-
7. Re: Can't connect to https webservices from my deployed .war. Please help!!!
jaikiran Jul 28, 2011 12:04 PM (in response to jaikiran)jaikiran pai wrote:
Matt Steedle wrote:
A snippet of the relevent code is:
String wsdlURL = "https://www.paypalobjects.com/wsdl/PayPalSvc.wsdl";
The https port in that configuration you posted is 8443. So the URL should have that port number.
Darran corrected me over IRC about this I did not pay attention that you are connecting to a different server and not your own. So I was wrong about the port.
-
8. Re: Can't connect to https webservices from my deployed .war. Please help!!!
msteedle Jul 28, 2011 12:04 PM (in response to jaikiran)The URL cannot be accessed on that port.
https://www.paypalobjects.com:8443/wsdl/PayPalSvc.wsdl does not load. I have no control over what ports the URL is open on.
-
9. Re: Can't connect to https webservices from my deployed .war. Please help!!!
msteedle Jul 28, 2011 12:06 PM (in response to jaikiran)jaikiran pai wrote:
jaikiran pai wrote:
Matt Steedle wrote:
A snippet of the relevent code is:
String wsdlURL = "https://www.paypalobjects.com/wsdl/PayPalSvc.wsdl";
The https port in that configuration you posted is 8443. So the URL should have that port number.
Darran corrected me over IRC about this I did not pay attention that you are connecting to a different server and not your own. So I was wrong about the port.
Any idea how to fix it then?
-
10. Re: Can't connect to https webservices from my deployed .war. Please help!!!
asoldano Jul 28, 2011 1:19 PM (in response to msteedle)I agree with Darran saying that the server side https connector configuration does not matter here, given the user is interested in a pure client webservice usage.
This said, there's no ws specific configuration for invoking an endpoint that's serverd over HTTPS. Matt, did you properly configure the ssl props? Something like:
System.setProperty("javax.net.ssl.trustStore", "/dati/truststore_abc");
System.setProperty("javax.net.ssl.trustStorePassword", "changeit");
System.setProperty("javax.net.ssl.trustStoreType", "jks");
-
11. Re: Can't connect to https webservices from my deployed .war. Please help!!!
asoldano Jul 28, 2011 1:23 PM (in response to asoldano)The "Client side" section should still apply for JBossWS 4 / JBoss AS 7: http://community.jboss.org/wiki/JBossWS-SecureTransport
-
12. Re: Can't connect to https webservices from my deployed .war. Please help!!!
msteedle Jul 28, 2011 3:32 PM (in response to asoldano)I will try this and let you know how it goes.
-
13. Re: Can't connect to https webservices from my deployed .war. Please help!!!
msteedle Jul 28, 2011 4:04 PM (in response to msteedle)I set the following properties in standalone.xml and it still didn't work.
<property name="javax.net.ssl.keyStore" value="C:\jboss-as-web-7.0.0.Final\standalone\configuration\client.keystore"/>
<property name="javax.net.ssl.trustStore" value="C:\jboss-as-web-7.0.0.Final\standalone\configuration\client.truststore"/>
<property name="javax.net.ssl.keyStorePassword" value="123456"/>
<property name="javax.net.ssl.trustStorePassword" value="123456"/>
<property name="javax.net.ssl.keyStoreType" value="jks"/>
<property name="javax.net.ssl.trustStoreType" value="jks"/>
<property name="org.jboss.security.ignoreHttpsHost" value="true"/>
After doing some debuging, I get the folloeing exception:
java.security.NoSuchAlgorithmException: SunTlsRsaPremasterSecret KeyGenerator not available
-
14. Re: Can't connect to https webservices from my deployed .war. Please help!!!
asoldano Jul 29, 2011 5:03 AM (in response to msteedle)An issue with JCE providers? This might be interesting http://stackoverflow.com/questions/2872520/suntlsrsapremastersecret-keygenerator-not-available