MIC does not match identical MIC

3 posts / 0 new

Wed, 2009-07-08 02:55

cbayes

Hi All,

I'm new to m-e-c, so this may be in a forum some where that I've missed.

I sent a file to a remote server, sync MDN requested. I received the MDN back with at state of [processed]. However, I'm seeing the following message in the log:

[7:38:41 PM] MOKOserver02-environ2-12232374e50-2840466server02@environ02: The Message Integrity Code (MIC) does not match the sent AS2 message (required: kvIEoILs3pE05Xn2J31ICOdqeT4=, sha1, returned: kvIEoILs3pE05Xn2J31ICOdqeT4=,sha1).

The only difference that I see is the space after the comma between the MIC and hash. Is this a known issue, or am I missing something on this?

Thanks!

Chuck

PS - here's my environment:

mendelson opensource AS2
1.1 build 27
Build date: 11.03.09 16:58

Wed, 2009-07-08 10:25

heller

cbayes,

its an unknown issue so far. Anyway you are right, these values should be identical. Even if we havent seen the header value without a blank so far the RFC 4130 says the following:

AS2-received-content-MIC-field =
"Received-content-MIC" ":" encoded-message-digest ","
digest-alg-id CRLF

It will be fixed in the next release, thank you for the feedback.

Regards
Heller

Fri, 2009-07-10 08:13

(Reply to #2) #3

cbayes

Hi Heller,

Thanks for your feedback, and for having such a great application.

Best Regards,
Chuck

You are here

MIC does not match identical MIC