Skip to Content
avatar image
Former Member

b2b as2 sender problem

After reading the blogs and helpful threads, I have run AS2 demo successfully with mendelson 😊.

But I still have problem to receice AS2 from WalMart.

find error in b2bic log:

AS2_VERSION: 1.1; MESSAGE_ID: <20141226041451A0B7256E@146907777000001>; AS2_TO: CC_AS2_SENDER_WALMART; AS2_FROM: 146907777000001; FROM: GVBe2Bzy; SUBJECT: EDIINTDATA; CONTENT_TYPE: application/pkcs7-mime; smime-type=enveloped-data; name="smime.p7m"; CONTENT_LENGTH:1351

Cannot decrypt message

Error occured while decrypting the AS2-message: Cannot decrypt message: org.bouncycastle.cms.CMSException: key invalid in message.

I did some search, somy says it is JCE problem?

but my demo scenario use 1024bits, it works fine.

or algorithm 3DES to DES, PI does not support 3DES? I use DES in my demo too.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Dec 29, 2014 at 01:13 PM

    Hi,

    We had this issue when we first started testing with longer keys and we followed the steps in this blog to have the system work for unlimited strength keys:

    B2B Adapters - Updating to JCE Unlimited Strength Jurisdiction Policy

    Regards,

    Ryan Crosby

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 31, 2014 at 02:41 AM

    Another problem, when send MDN to walmart:


    Cannot send MDN: com.sap.httpclient.exception.NoHttpResponseException: The server gem.wal-mart.com is not responding


    We have received EDI data, but failed to send MDN back.


    network problem or configuration?


    Thanks


    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Dimitri Sannen

      Hi Dimitri and Ryan,

      Thanks for your support.

      Telnet with port command was fine and the server is up also.Identified the problem like the Own AS2 name in AS2 Receiver channel is different with the one in the VAN Mail Box portal .In Mail Box it was wrongly configured .Corrected and In PI monitoring it starts showing successfully delivered the messages.

      Thanks,

      Tibin.