cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <>
Subject Re: CXF over HTTPS on Glassfish and Tomcat
Date Thu, 11 Sep 2008 17:44:39 GMT

At what point is it failing?   During client creation or while actually 
invoking a method?    

That's important.   Right now, we don't have anyway to retrieve the wsdl's via 
custom SSL/HTTPS stuff.  Thus, if it's during the client creation, it's most 
likely trying to retrieve the wsdl and that's not working.   

If it's the latter case, it's USUALLY a wrong qname on the http-conf node.   
Not sure how to debug that though.


On Monday 08 September 2008 8:54:30 am Łukasz Pijanowski wrote:
> On Wed, Aug 20, 2008 at 12:05 PM, Łukasz Pijanowski
> <> wrote:
> > Do you have any ideas what may cause the broken connection?
> First of all, thank you guys for your help:-)
> I've done some debugging and I've found out that CXF web service
> client does not provide a certificate to the CXF web service provider.
> As I wrote above, CXFServlet is a part of my enterprise application
> under Glassfish. When I access the web service URL I am able to
> authenticate and see the web service's WSDL. Proper authentication
> real is being invoked (checked by debugging) during that process.
> However, when I use the same link to access it from CXF client
> (configured via Spring) the connection gets interrupted as the client
> does not provide that proper certificate.
> Both the certificate and the private key are available in key stored
> configured in <sec:keyStore> node in CXF configuration.
> Do you know why client does not present the certificate to the web
> service provider during SSL handshake?
> Cheers!

Daniel Kulp

View raw message