If you can see the WSDL from a browser after installing the certificates, then the service side must be fine. In that case, the issue seems to be with the certificates. Per step 1 of the earlier link:
1. Create a server key and have it trusted by the SOAP client
-->1.1 Create a server key
-->1.2 import the server's public key into the web service client's truststore
----->1.2.1 Export the certificate from the server keystore into a file
----->1.2.2 Then import the certificate into the SOAP client's truststore
2. Activate the SSL port on the
JEE Server
3. Add users and a new role to the application server
4. Update the web.xml to require SSL and basic authentication
5. Update the soap:address in the WSDL's service section to use the https protocol and port
6. Redeploy the web service
7. Update the SOAP client to provide the basic auth username and password
Assuming that step 1.1, 2, 4, 5, and 6 are setup correctly on the server, and step 7 is the client which should be fine I think because its simple enough. Some questions:
a) What method are you using to verify that step 1.2.1 and 1.2.2 are done correctly as required? You could try using something like this: keytool -list -keystore client.jks -storepass ClientJKS (client.jks is the file from step 1.2.2)
b) Can you confirm that on the server side, the userid/password are setup as required, e.g. the
tomcat example in the link where an entry is added in server.xml?
c) In the link, the updated client code has this line "System.out.println("Using URL: " + urlUsed);". Please post the URL used, including the secure port#. Does this match the WSDL URL you enter in the browser?
d) What technologies are used on the server? I mean like Metro/Glassfish/Axis, etc.
e) Regarding
#5 created client with local wsdl on netbeans
the local WSDL does have the complete
remote WSDL URL, right? Just want to confirm.
f) are you generating this client in Netbeans based on the wsdl? if yes, then how are you specifying the truststore? And how are you executing it? Take a look at this
Secure Calculator tutorial in Netbeans. See if you develop your client in the same way?
g) Regarding
System.setProperty("javax.net.ssl.trustStore", "...\key.jks");
maybe you can turn on logging and see if it is actually finding your truststore. Try running your client program using -Djavax.net.debug=all. See
here for what I mean. This might provide you clues as to the problem.
How are you importing your .crt to .jks? Please see
Import a root or intermediate CA certificate to an existing Java keystore for an example. As William Brogden mentioned earlier, maybe the request is not even sent?
Or maybe it can't find the keystore?
If you still have problems after looking into and trying all of the above
then please post more details about your server and client environments, your client code (the minimum necessary), etc. and I can try to duplicate it.
Whatever it is, kindly post your solution here once you have it - I am sure it will be soon.
Best of luck!
, is it sent from the server? what does the error mean actually?
