Home » Forum » Software » Open Source Software » mec as2 » m-e-c as2 compatibility

IP*Works! EDI AS2 connector

nicolas.roumiantzeff

I have checked compatibility between IP*Works! EDI AS2 Connector against the Mendelson-e-commerce GmbH test server (http://www.mec-as2.org/).

It works except that among the 4 test files I have sent, one fails in the signature verification (see below). Note that this error might be the same as the one described in this forum at: http://www.mec-community.com/node/219

[1/30/08 9:56:45 AM]
mendAS2-1201683405723-138@mendelsontestAS2_mycompanyAS2: MDN created, state
set to [processed/error: authentication-failed].

[1/30/08 9:56:45 AM]
20973963-7ea8-4a2c-8401-8ff951245c08@aec5eb51-a10e-4314-912d-c74de65c21f0:
MDN details:
--------------
Error verifying the senders digital signature: invalid signature format in message:
content hash found in signed attributes different.
--------------

‹ Nubridges Commerce Suite Server Working with Cleo VL Trader ›

Submitted by nicolas.roumiantzeff on Wed, 2008-01-30 11:30.

admin
nicolas,

nicolas,

the test server is tested fairly often using the product you mentioned, without this problem so far. Are you sure you used the right key to sign your message? This is what the test servers log writes to your attempts:

[1/30/08 9:56:45 AM]
20973963-7ea8-4a2c-8401-8ff951245c08@aec5eb51-a10e-4314-912d-c74de65c21f0: Using
certificate "Key1" to verify signature.

[1/30/08 9:56:45 AM]
mendAS2-1201683405723-138@mendelsontestAS2_mycompanyAS2: Outgoing MDN has been
signed with the algorithm "SHA1".

[1/30/08 9:56:45 AM]
mendAS2-1201683405723-138@mendelsontestAS2_mycompanyAS2: MDN created, state
set to [processed/error: authentication-failed].

Could you please ensure that you are using key1 to sign your message?

Regards
Heller


Wed, 2008-01-30 13:34

jerich0
Look at this

I send files from IPWorks to MEC. Some files are received succesfull, but some files receive MDN error [processed/error: authentication-failed]. I tryed to use openssl and portecle to generate certs for MEC and IPWorks. First file is successfull, next fail. MEC build 25

[9:52:04 AM] f79acb2b-910a-4c61-a417-52f30e350065@1a16d8c2-1719-4c72-baa5-3725cb878688: Incoming transmission is a AS2 message, raw message size: 13.00 KB.
[9:52:04 AM] f79acb2b-910a-4c61-a417-52f30e350065@1a16d8c2-1719-4c72-baa5-3725cb878688: AS2 message is encrypted.
[9:52:04 AM] f79acb2b-910a-4c61-a417-52f30e350065@1a16d8c2-1719-4c72-baa5-3725cb878688: The data has been decrypted using the key "Key1".
[9:52:04 AM] f79acb2b-910a-4c61-a417-52f30e350065@1a16d8c2-1719-4c72-baa5-3725cb878688: AS2 message is signed.
[9:52:04 AM] f79acb2b-910a-4c61-a417-52f30e350065@1a16d8c2-1719-4c72-baa5-3725cb878688: The sender used the algorithm SHA1 to sign the message.
[9:52:04 AM] f79acb2b-910a-4c61-a417-52f30e350065@1a16d8c2-1719-4c72-baa5-3725cb878688: Using certificate "IPWorks" to verify signature.
[9:52:04 AM] f79acb2b-910a-4c61-a417-52f30e350065@1a16d8c2-1719-4c72-baa5-3725cb878688: Digital signature verified successful.
[9:52:04 AM] mec_as2-1222926724911-4@local_IPWorks: Outgoing MDN has not been signed.
[9:52:04 AM] mec_as2-1222926724911-4@local_IPWorks: MDN created, state set to [processed].
[9:52:04 AM] mec_as2-1222926724911-4@local_IPWorks: Synchronous MDN sent as answer to message f79acb2b-910a-4c61-a417-52f30e350065@1a16d8c2-1719-4c72-baa5-3725cb878688.
[9:52:04 AM] f79acb2b-910a-4c61-a417-52f30e350065@1a16d8c2-1719-4c72-baa5-3725cb878688: AS2 communication successful, payload 1 has been moved to "/srv/as2/mec/messages/local/inbox/IPWorks/f79acb2b_910a_4c61_a417_52f30e350065@1a16d8c2_1719_4c72_baa5_3725cb878688".
[9:52:26 AM] 87a5418f-4b9c-43e5-b19f-9f17d33ff8bb@dd6489f6-09d7-4634-9c85-e7f49bfa81bb: Incoming transmission is a AS2 message, raw message size: 104.00 KB.
[9:52:26 AM] 87a5418f-4b9c-43e5-b19f-9f17d33ff8bb@dd6489f6-09d7-4634-9c85-e7f49bfa81bb: AS2 message is encrypted.
[9:52:26 AM] 87a5418f-4b9c-43e5-b19f-9f17d33ff8bb@dd6489f6-09d7-4634-9c85-e7f49bfa81bb: The data has been decrypted using the key "Key1".
[9:52:26 AM] 87a5418f-4b9c-43e5-b19f-9f17d33ff8bb@dd6489f6-09d7-4634-9c85-e7f49bfa81bb: AS2 message is signed.
[9:52:26 AM] 87a5418f-4b9c-43e5-b19f-9f17d33ff8bb@dd6489f6-09d7-4634-9c85-e7f49bfa81bb: The sender used the algorithm SHA1 to sign the message.
[9:52:26 AM] 87a5418f-4b9c-43e5-b19f-9f17d33ff8bb@dd6489f6-09d7-4634-9c85-e7f49bfa81bb: Using certificate "IPWorks" to verify signature.
[9:52:26 AM] mec_as2-1222926746259-5@local_IPWorks: Outgoing MDN has not been signed.
[9:52:26 AM] mec_as2-1222926746259-5@local_IPWorks: MDN created, state set to [processed/error: authentication-failed].
[9:52:26 AM] 87a5418f-4b9c-43e5-b19f-9f17d33ff8bb@dd6489f6-09d7-4634-9c85-e7f49bfa81bb:
MDN details:
--------------
Error verifying the senders digital signature: invalid signature format in message: content hash found in signed attributes different.
--------------
[9:52:26 AM] mec_as2-1222926746259-5@local_IPWorks: Synchronous MDN sent as answer to message 87a5418f-4b9c-43e5-b19f-9f17d33ff8bb@dd6489f6-0


Thu, 2008-10-02 08:33

heller
heller's picture
jerich0, I made tests

jerich0,

I made tests sending some hundred messages from one sender to m-e-c as2 at once and no problem occured. Are you sure the problem is not on the sender site?

Is there anybody else in the community who encountered this problem?

Regards
Heller


Thu, 2008-10-02 09:53

jerich0
Also

In my cosole output I have this message.

Oct 2, 2008 1:36:38 PM de.mendelson.comm.as2.message.AS2MessageParser decryptData
INFO: 62d27c25-3dbe-4fa5-af64-1a51c0624818@e128a725-ca3a-41a4-bb79-0db62b8c8b41: The data has been decrypted using the key "local".
Oct 2, 2008 1:36:38 PM de.mendelson.comm.as2.message.AS2MessageParser verifySignature
INFO: 62d27c25-3dbe-4fa5-af64-1a51c0624818@e128a725-ca3a-41a4-bb79-0db62b8c8b41: AS2 message is signed.
java.security.NoSuchAlgorithmException: no such algorithm: 1.3.14.3.2.26 for provider BC
at sun.security.jca.GetInstance.getService(GetInstance.java:70)
at sun.security.jca.GetInstance.getInstance(GetInstance.java:190)
at java.security.Signature.getInstance(Signature.java:324)
at de.mendelson.util.security.BCCryptoHelper.convertOIDToAlgorithmName(BCCryptoHelper.java:422)
at de.mendelson.comm.as2.message.AS2MessageParser.getDigestFromSignature(AS2MessageParser.java:428)
at de.mendelson.comm.as2.message.AS2MessageParser.verifySignature(AS2MessageParser.java:391)
at de.mendelson.comm.as2.message.AS2MessageParser.createMessageFromRequest(AS2MessageParser.java:189)
at de.mendelson.comm.as2.server.AS2ServerRemoteImpl.newMessageArrived(AS2ServerRemoteImpl.java:129)
at de.mendelson.comm.as2.server.AS2ServerRemoteImpl.computeServerSite(AS2ServerRemoteImpl.java:304)
at de.mendelson.comm.as2.server.AS2ServerRemoteImpl.execute(AS2ServerRemoteImpl.java:97)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
Oct 2, 2008 1:36:38 PM de.mendelson.comm.as2.message.AS2MessageParser verifySignature
INFO: 62d27c25-3dbe-4fa5-af64-1a51c0624818@e128a725-ca3a-41a4-bb79-0db62b8c8b41: The sender used the algorithm SHA1 to sign the message.
Oct 2, 2008 1:36:38 PM de.mendelson.comm.as2.message.AS2MessageParser verifySignature
INFO: 62d27c25-3dbe-4fa5-af64-1a51c0624818@e128a725-ca3a-41a4-bb79-0db62b8c8b41: Using certificate "IPWorks" to verify signature.


Thu, 2008-10-02 11:38

heller
heller's picture
jerich0, I encountered this

jerich0,

I encountered this message myself yesterday and have seen that this is a debug statement to test the signature class that runs on an error, please ignore this message. OID 1.3.14.3.2.26 is SHA-1 and it's available in the crypto API.

But to your problem: I will install IPWorks later and fire some messages to m-e-c as2 to see if I can reproduce your problem.

Regards
Heller


Thu, 2008-10-02 11:43

jerich0
OK

I checked
freeas2.com IPWorks AS2 CONNECTOR V2 [VERSION: 2.0.3155.0] IPWorks! EDI AS2 Connector V1. Both have same simptoms.
I checked m-e-c b23 and b25 on RHEL 2.6.18-8.el5 #1 SMP x86_64 x86_64 x86_64 GNU/Linux,

java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) 64-Bit Server VM (build 10.0-b23, mixed mode)


Thu, 2008-10-02 11:53

jerich0
Content Transfer Encoding

it looks like content transfer encoding problem


Thu, 2008-10-02 15:32

jerich0
Try to give to IPWorks files

Try to give to IPWorks files in differnet codepages. Some files are received successfull. Some files receive MDN auth error when checking digital sign. I turn off encryption in raw log i found characters which cannot be shown here. There is encoding problem and maybe on IPWorks side.


Thu, 2008-10-02 15:48

heller
heller's picture
jerich0, could you please

jerich0,

could you please send me the source of your test client and some test files?

sh at mendelson dot de

Regards
Heller


Thu, 2008-10-09 13:25


© 1999-2008 mendelson-e-commerce GmbH. All right reserved.