Seeburger AS2: MD5WithRSAEncryption NoSuchAlgorithmException

[Former Member]

Hello,

we use a AS2 receiver communication channel with SSL encryption. However when sending out a message we get the following error.

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: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: MD5WithRSAEncryption, provider: BC, class: org.bouncycastle.jce.provider.JDKDigestSignature$MD5WithRSAEncryption), SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: java.io.IOException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: MD5WithRSAEncryption, provider: BC, class: org.bouncycastle.jce.provider.JDKDigestSignature$MD5WithRSAEncryption)

We already checked that all Java Policy Files have been deployed. We have also tested the adapter successfully.

Any ideas on this?

Thank you!

[Former Member · Accepted solution]

Hi Florian,

Can you please let us know the options that you have used in the receiver AS2 adapter?

Thanks,

Srini

[Former Member · Accepted solution]

Hello,

here are the options that we use:

Transport Protocol : HTTPS

MDN Mode: Synchronous

AS2: Sign, Signing Algorithm: MD5 (probably this causes the issue?)

Is there anything else you need?

[Former Member]

Our basis team had the adapter restarted which solved the problem.

[Former Member]

You might have deployed without restarting afterwards ?

[Former Member]

Hi Florian,

have you checked the following:

-Installation of the Java Cryptography Extension?

-Did you deploy SeeCryptoSourceBridgeLibXI.sda? (Seeburger Certificate Service)

-The Exception "java.io.IOException: java.security.NoSuchAlgorithmException: Error constructing implementation" could also point to a problem in the Keystore:

--> Did you create an Adapter User to access the Keystore?

--> Check if you have set the view_creator role of the keystore you are using to EVERYONE.

--> Maybe your certificate is corrupt?

regards,

Daniel

[markangelo_dihiansan]

Hi Florian,

As far as I know, MD5 was pronounced officially insecure as early as 4th quarter 2008. Users were advised to move to the more secure SHA-1 algorithm. This is what may be causing the error because the algorithm was already removed as a way to sign certificates. You may check security sites to confirm this.

Hope this helps,

[Former Member]

Florian,

Can you see the full stack trace for this error (in the J2EE trace or log files) ?

Chris