PI 7.3 Seeburger AS2 receiver adapter error

[Former Member]

Hi All,

We are getting error while sending data from PI to 1SYNC(AS2 Receiver adapter).

Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: java.io.IOException: key inappropriate for algorithm., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: java.io.IOException: key inappropriate for algorithm.

Error type: COMPONENT_ERROR >> Error date: 5/9/13 2:45 PM >> Description: AS2 Adapter failure java.lang.Exception: AS2 message composition failed: java.io.IOException: key inappropriate for algorithm. com.seeburger.as2.AS2Plugin.execute(AS2Plugin.java:379) [5/9/13 2:45 PM]

Referred the following thread.

https://scn.sap.com/thread/1752623  still facing the same issue.

Configuration:

In AS2 RCC: Signing algorithm - SHA1

                   Encryption - 3DES

In receiver agreement:

        Signing key : Generated in PI

        Encryption certificate: Provided by 1SYNC

Can you please let me know what might be the issue.

Regards,

Sreenivas.

[Former Member · Accepted solution]

The issue has been resolved after BASIS has updated the JAVA CRYPTO file with latest version.

Regards,

Sreenivas.

[former_member223322]

Does the signing key has SHA1WithRSA algorithm in the signature (you can check this NWA/Key-storage)? Also make sure that the receiver has the updated decryption key.

~Srini

[Former Member]

Hi Srinivasan,

Yes, the key is having signing algorithm as 'sha1WithRSAEncryption'.

Also make sure that the receiver has the updated decryption key

you mean 1SYNC should have updated decryption key ?

Regards,

Sreenivas.

[former_member223322]

Yes, the 1SYNC ( I believe this is the receiver) should have the updated certificate that has been generated in SAP PI.

~Srini

[Former Member]

Yes, we provided updated certificate.

Sreeni.

[former_member223322]

Check with the receiver if they have the same Signing key & Algorithm settings at their end. This is just a handshake error and you need to check with the receiver if they have uploaded and are using the updated cert that you had provided.

~Srini