Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Discover how organizations are unlocking new revenue streams: Watch here
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

cCXF SSL :javax.net.ssl.SSLHandshakeException: SSLHandshakeException

Hello Everyone ,
I have usecase where using cCXF component to consume  external https based webservice and this webservice requires an ssl certificate to communicate.
We have loaded the certificate in a keystore and configured runtime with  etc/ org.apache.cxf.http.conduits-test.cfg   with tls parameters as below and deployed this route having cCXF  but ended up with 
Caused by: javax.net.ssl.SSLHandshakeException: SSLHandshakeException invoking  : Received fatal alert: handshake_failure
Is this correct way of consuming a service with cCXF . Do we need to write any extra bean code in mediation like 
here in section   CONFIGURING SSL SUPPORT ?

______________________________________________________________
org.apache.cxf.http.conduits-token.cfg 
url = https://localhost.*
client.ConnectionTimeout = 20000 client.ReceiveTime

To see the whole post, download it here
Labels (5)
4 Replies
Anonymous
Not applicable
Author

Hi
don't you miss the "url" property from your conduit file?
g.
Anonymous
Not applicable
Author

Hi , 
Thank you for reply .I do have url on the http conduits . Edited the post with full file .
But my route is like below
cCXF(http://localhost:8089/testService) ->cProcessor-> cCXF(https :// externa-webservice)  
will this service pick settings of ssl from http conduits ?
Thanks,
Nitesh
Anonymous
Not applicable
Author

Hi , 
Thank you for reply .I do have url on the http conduits . Edited the post with full file .
But my route is like below
cCXF(http://localhost:8089/testService) ->cProcessor-> cCXF(https :// externa-webservice)  
will this service pick settings of ssl from http conduits ?
Thanks,
Nitesh

I believe the "org.apache.cxf.http.conduits-common.cfg" config is used for the localhost, however now I see the same truststore and url is used 0683p000009MPcz.png To go really deeply, you can start the container with -Djavax.net.debug=ssl and you will see which keystore, truststore is really loaded and used.
and looking at trace, try to use the url for " 192.168.101.25", not localhost
g.
Anonymous
Not applicable
Author

Thank you  for help Gabriel . On modifying 
org.apache.cxf.http.conduits-token.cfg 
url = https://localhost.*
to 
url =https://<external-service>.*   
made the cxf client on runtime to pick certificate from keystore pointed in org.apache.cxf.http.conduits-token.cfg 

Thanks,
Nitesh