How to install an SSL Cert for a JAX-WS Service?

[Mike London]

After getting the the certification zip file back from the provider (GO DADDY), I notice that there are 4 files in the zip!

Huh?

The only resource I have says to point tomcat at the single keystore file via server.xml and also gives instructions on how to modify the client JAX-WS.

I'm assuming that the zip file is not the keystore file, or is it?

So, my question is, since this certificate did not come from a "top-tier" CA, how do I go about getting Tomcat to use it?

This may sound like a Tomcat question, but actually, I need to get my JAX-WS service to use this once Tomcat is happy.

Thanks to all for any help or suggestions.

-- Mike

[Ivan Krizsan]

Hi!
First of all, I assume you will need a SSL connector in Tomcat. This is also where you will install the certificate for the web service.
Good instructions are available at: http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html
Note that the default SSL connector uses port 8443, which you may want to change to port 443.
Second, you also need to configure the web.xml deployment descriptor of the web service like this:

<?xml version="1.0" encoding="UTF-8"?> 
<web-app 
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
    xmlns="http://java.sun.com/xml/ns/javaee" 
    xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" 
    xsi:schemaLocation=" 
        http://java.sun.com/xml/ns/javaee 
        http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" 
        id="WebApp_ID" version="2.5"> 
    <display-name>JAX-WS_GreetingServletMutualAuth</display-name> 
    <security-constraint> 
        <display-name>SecurityConstraint</display-name> 
        <web-resource-collection> 
            <web-resource-name>Secure Area</web-resource-name> 
            <url-pattern>/HelloWorldWSService</url-pattern> 
            
            <!-- 
                JSR-109 specifies that http-method POST must be used. 
                If we include GET here, access to the WSDL will also 
                be protected, otherwise not. 
             --> 
            <http-method>POST</http-method> 
        </web-resource-collection> 
        
        <!-- 
            Plain SSL and mutual authentication both require CONFIDENTIAL 
            transport-guarantee to be configured. 
        --> 
        <user-data-constraint> 
            <transport-guarantee>CONFIDENTIAL</transport-guarantee> 
        </user-data-constraint> 
    </security-constraint> 
</web-app>

Let me know if the above does not work for you.
Good luck!