Trying to get 1.1 r27 to work with iSoft Commerce Suite Server.
Sending to the iSoft Server from Mendelson AS2 works!
Receiving reports success on Mendelson side. However the iSoft server reports that the MDN was not signed.
The iSoft log:
ADMIN1: 2009.05.04 15:57:28:675 1628602591 HPOS OK HTTP outbound session started - workorder=(221531444) mbox=(Fnr8SkV7) batch=(#1031233) attempt=(1 of 1)
ADMIN1: 2009.05.04 15:57:45:678 1628602591 HPOS OK HTTP outbound client: AS2Local
ADMIN1: 2009.05.04 15:57:46:360 1628602591 EXCE OK File extracted - (252) bytes
ADMIN1: 2009.05.04 15:57:46:614 PNOC OK ** Batch (1031233) (EDIINTDATA) CONNECT notice for TxnId 1628602591 stored in database **
ADMIN1: 2009.05.04 15:57:46:761 1628602591 PHDR OK HTTP Response-Line = (HTTP/1.1 200 OK)
ADMIN1: 2009.05.04 15:57:46:818 1628602591 VRFY ERR Signature not verified
ADMIN1: 2009.05.04 15:57:46:820 1628602591 HPOS ERR One or more errors occurred with this transaction. m_nErr=(2106)
ADMIN1: 2009.05.04 15:57:46:871 PNOC OK ** Batch (1031233) (EDIINTDATA) SEND notice for TxnId 1628602591 stored in database **
ADMIN1: 2009.05.04 15:57:47:079 1628602591 HPOS OK HTTP outbound session stopping - batch=(#1031233)
The Mendelson log:
[May 4, 2009 3:57:46 PM] 2009050414572986D27585@non-EDI_8923749889723: Incoming transmission is a AS2 message, raw message size: 2.02 KB.
[May 4, 2009 3:57:46 PM] 2009050414572986D27585@non-EDI_8923749889723: AS2 message is encrypted.
[May 4, 2009 3:57:46 PM] 2009050414572986D27585@non-EDI_8923749889723: The data has been decrypted using the key "as2".
[May 4, 2009 3:57:46 PM] 2009050414572986D27585@non-EDI_8923749889723: AS2 message is signed.
[May 4, 2009 3:57:46 PM] 2009050414572986D27585@non-EDI_8923749889723: The sender used the algorithm SHA1 to sign the message.
[May 4, 2009 3:57:46 PM] 2009050414572986D27585@non-EDI_8923749889723: Using certificate "nonedi8923749889723" to verify signature.
[May 4, 2009 3:57:46 PM] 2009050414572986D27585@non-EDI_8923749889723: Digital signature verified successful.
[May 4, 2009 3:57:46 PM] 2009050414572986D27585@non-EDI_8923749889723: Found 1 payload attachments in the message.
[May 4, 2009 3:57:46 PM] Soflex_AS2-1241467066462-166@ASLocal_non-EDI_8923749889723: Outgoing MDN has been signed with the algorithm "SHA1".
[May 4, 2009 3:57:46 PM] Soflex_AS2-1241467066462-166@ASLocal_non-EDI_8923749889723: MDN created, state set to [processed].
[May 4, 2009 3:57:46 PM] Soflex_AS2-1241467066462-166@ASLocal_non-EDI_8923749889723: Synchronous MDN sent as answer to message 2009050414572986D27585@non-EDI_8923749889723.
[May 4, 2009 3:57:46 PM] 2009050414572986D27585@non-EDI_8923749889723: AS2 communication successful, payload 1 has been moved to "/opt/as2mec/messages/AS2Local/inbox/2009050414572986D27585@non_EDI_8923749889723".
Any ideas?
will,
the AS2 message contains a HTTP header that indicates if the MDN should be signed or not, this option should be found in the senders settings.
sample for this header:
disposition-notification-options = signed-receipt-protocol=optional, pkcs7-signature; signed-receipt-micalg=optional, sha1, md5
Please have a look at this header in the senders outbound AS2 message to see if the MDN should be signed or not.
But beneath this, by looking at your sent log: Are you sure that the MDN isnt signed or is there a verfication problem with the signature? (Please check the cert settings in this case).
Regards
Heller
Not really sure how to parse that.
This is the header from the MDN sent:
will,
if the mendelson opensource AS2 solution sends an MDN with the content type "multipart/signed", the MDN should be signed. Is there a problem with the signature, isnt the MDN signed? Or is it signed and the receiver could not verify the signature?
Regards
Heller