Error verivying the sendes digital signature openAs2 -> mec
eingfoan
hi *,
i am testing interoperability with openas2. to me a very strange thing occurs:
when trying to send plain text (ascii) data from openas2 to mec everything is fine. when i am trying to send binary data e.g. word documents from openas2 to mec the following error occurs:
[11:15:44 AM] OPENAS2-18042008111538+0200-3702@OpenAS2A_as2.spar.at: Incoming transmission is a AS2 message, raw message size: 29.00 KB.
[11:15:44 AM] OPENAS2-18042008111538+0200-3702@OpenAS2A_as2.spar.at: AS2 message is encrypted.
[11:15:44 AM] OPENAS2-18042008111538+0200-3702@OpenAS2A_as2.spar.at: The data has been decrypted using the key "spar".
[11:15:44 AM] OPENAS2-18042008111538+0200-3702@OpenAS2A_as2.spar.at: AS2 message is signed.
[11:15:44 AM] OPENAS2-18042008111538+0200-3702@OpenAS2A_as2.spar.at: Using certificate "openas2a" to verify signature.
[11:15:44 AM] mec_as2-1208510144915-6@as2.spar.at_OpenAS2A: Outgoing MDN has been signed with the algorithm "SHA1".
[11:15:44 AM] mec_as2-1208510144915-6@as2.spar.at_OpenAS2A: MDN created, state set to [processed/error: authentication-failed].
[11:15:44 AM] OPENAS2-18042008111538+0200-3702@OpenAS2A_as2.spar.at:
MDN details:
--------------
Error verifying the senders digital signature: invalid signature format in message: content hash found in signed attributes different.
--------------
[11:15:44 AM] mec_as2-1208510144915-6@as2.spar.at_OpenAS2A: Synchronous MDN sent as answer to message OPENAS2-18042008111538+0200-3702@OpenAS2A_as2.spar.at.
i am not really shure which client / server is now having a problem with binary data. or do i do something wrong?
isn't it allowed to send binary data?
hi *,
i am testing interoperability with openas2. to me a very strange thing occurs:
when trying to send plain text (ascii) data from openas2 to mec everything is fine. when i am trying to send binary data e.g. word documents from openas2 to mec the following error occurs:
[11:15:44 AM] OPENAS2-18042008111538+0200-3702@OpenAS2A_as2.spar.at: Incoming transmission is a AS2 message, raw message size: 29.00 KB.
[11:15:44 AM] OPENAS2-18042008111538+0200-3702@OpenAS2A_as2.spar.at: AS2 message is encrypted.
[11:15:44 AM] OPENAS2-18042008111538+0200-3702@OpenAS2A_as2.spar.at: The data has been decrypted using the key "spar".
[11:15:44 AM] OPENAS2-18042008111538+0200-3702@OpenAS2A_as2.spar.at: AS2 message is signed.
[11:15:44 AM] OPENAS2-18042008111538+0200-3702@OpenAS2A_as2.spar.at: Using certificate "openas2a" to verify signature.
[11:15:44 AM] mec_as2-1208510144915-6@as2.spar.at_OpenAS2A: Outgoing MDN has been signed with the algorithm "SHA1".
[11:15:44 AM] mec_as2-1208510144915-6@as2.spar.at_OpenAS2A: MDN created, state set to [processed/error: authentication-failed].
[11:15:44 AM] OPENAS2-18042008111538+0200-3702@OpenAS2A_as2.spar.at:
MDN details:
--------------
Error verifying the senders digital signature: invalid signature format in message: content hash found in signed attributes different.
--------------
[11:15:44 AM] mec_as2-1208510144915-6@as2.spar.at_OpenAS2A: Synchronous MDN sent as answer to message OPENAS2-18042008111538+0200-3702@OpenAS2A_as2.spar.at.
i am not really shure which client / server is now having a problem with binary data. or do i do something wrong?
isn't it allowed to send binary data?
regards chris