Sander Fieten

Hi Christopher, I think there is an issue in OpenAS2 when you configure these digest algorithms differently. Although it seems a bit strange to use one algorithm for sending and expect another for the MDN it is allowed by the specification. So if you allow the OpenAS2 user to configure as such I would expect that this is also handled by OpenAS2 correctly. But you can of course also restrict this to just one algorithm for both the message and MDN [request options]. In that case I would add some remarks...

Hi, I am currently using OpenAS2 to test my own AS2 implementation and I am experiencing an issue with MDNs. When I use OpenAS2 to send a message to my implementation it is correctly received and a MDN is generated for the message. However the MDN is then rejected by OpenAS2 stating that the digest algorithm used for the calculation of the digest in the Received-Content-MIC field is incorrect. I used the example partnership configuration as baseline, disabling encryption and changing the certificates....

Hi, I am currently using OpenAS2 to test my own AS2 implementation and I am experiencing an issue with MDNs. When I use OpenAS2 to send a message to my implementation it is correctly received and a MDN is generated for the message. However the MDN is then rejected by OpenAS2 stating that the digest algorithm used for the calculation of the digest in the Received-Content-MIC field is incorrect. I used the example partnership configuration as baseline, disabling encryption and changing the certificates....

Fix to prevent further processing of an already...

Fix for NPE that occurred when a payload marked...

Patch to beta-2 for fixing a possible NPE when ...

Patch to beta-2 for fixing configuration errors...

Update to reflect actual implementation of payl...