Hi Rahul,

This error occurs only when proper ssl handshake didnt happen, most of the time this is due to the certificate not added to the truststore. Is the certificate added to the truststore ? You can use keytool like keytool -list to see all the certificates imported to the truststore.

FYI, this can be done at JVM level or at PRPC rule in the connect rule form.

Thanks,

Sudarsan M

Certificate is there in WAS.

However we found that in Connect Http level we again need to provide the Keystore, then only proper handshake happens.

Hi Rahul,

Do you mean that it is working fine for you now? we are having similar issue with a Connect SOAP. 

If fixed, can you please let me know the exact steps you followed to address it.

Thanks

Riadh

Enable Ws Security and create a Security Profile.

In Security p[rofile refer a Keystore

Keystore should have certificate appropriate certificate.

This resolves the issue and connection is established.

We have uploaded the certificates in trust store and using the same to connect, but still we keep seeing the issue, any thoughts from ppl above pls