on 08-01-2016 10:35 AM
Hi All,
PI 7.1
Seeburger AS2 adapter.
We are using Seeburger AS2 receiver adapter, running SAP PI 7.1 to communicate with external trading partner. This interface is working fine, until certificate is renewed. After the certificate renewal it's started throwing the following error. Error occurs during the SSL Handshake.
Error: Message could not be forwarded to the JCA adapter. Reason: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate # , SEEBURGER AS2: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate #
Error: MP: exception caught with cause javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate # , SEEBURGER AS2: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate #
Error: Adapter Framework caught exception: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate # , SEEBURGER AS2: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate #
Error: Delivering the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate # , SEEBURGER AS2: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate # .
I have gone all the other discussion on this issue on SCN.
My trading partner has confirmed that certificates are stored in TrustedCAs. I have also restarted our PI server.
Any ideas please?
Thanks in advance.
Vijay
Hi Vijay,
The problem is either that trading partner doesn't trust your public certificate or that the certificates were not updated in your PI.
Regards,
Mate
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mate,
Thanks for the reply. We have updated our certificates & restarted server. Trading partner has confirmed that they have our certificates. We are kind of stuck here without any ideas to try.
Is there any way intercept & capture SSL logs of communication with our trading partner, using something similar to XPI Inspector?
Will it possible to use XPI Inspector here?
Any ideas to try will be much appreciated.
Thanks
Vijay
Hello Vijay,
XPI should help you,But am not pretty much sure ,never heard any cases on seeburger with XPI still you can give a try.
And adding to this error this could be because of PI certificates not trusted by the vendor.Please double check if the PI public certificates are uploaded and trusted at the vendor side.
Also check the point mentioned by Nimrod ,ensure your pointing to new renewed certificates.
Make sure you have updated the certificate in the relevant AS2 channel as well.
And in the Sender agreement as well...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.