Vyacheslav Stetskevych

No, actually it's not the case. Only one cert is required for signing and encryption.

Does OpenAS2 support separate certificates for Signing and Encryption? It seems like I have this exact case.

I have their public certificate installed. I think I only need the leaf certificate, or should I also include the chain (intermediate + root)? The one trading partner that I have working in OpenAS2, I only use the leaf certificate with that connection.

Tested sending a file with -Dsun.net.http.allowRestrictedHeaders=true, did not help.

Here is the log from our (OpenAS2) side. The trading partner sent us 4 test messages. 2 with a SHA1 certificate, and 2 with a SHA2 certificate. MIMEBodyPart logging was enabled. Please review, if you can produce any hints from this. Thanks!

Removing compression did not help. Switching to binary transfer also did not help. Mimebodypart is on and I will ask them to send us a message. The partner sent me a diagnostic email with the headers I am sending vs headers other (working) partners send them. Although these are headers from an OpenAS2 fork I tested one time (by phax), it should be something similar because the error is the same with the fork as with the original OpenAS2. (I am now testing with the original, and the log attached above...

<partnership name="ONE-to-TWO"> <sender name="ONE"/> <receiver name="TWO"/> <attribute name="protocol" value="as2"/> <attribute name="content_transfer_encoding" value="8bit"/> <attribute name="compression_type" value="ZLIB"/> <attribute name="subject" value="From ONE to TWO"/> <attribute name="mdnsubject" value="Your requested MDN response from $receiver.as2_id$"/> <attribute name="as2_url" value="https://two:443/receiveas2"/> <attribute name="as2_mdn_to" value="one@one.com"/> <!-- <attribute name="as2_receipt_option"...

I've set up a connection from OpenAS2 2.3.0 to WebMethods. One issue is described in https://sourceforge.net/p/openas2/discussion/265568/thread/1494c1fe/ (I still get an HTML MDN message), but this thread is about another issue. The MDN text I receive back from WebMethods says: Status: processed/error: insufficient-message-security I've inquired the WebMethods end (a trading partner) about the error. And they told us the following: The message is not signed and encrypted, only encrypted. Can you...