AS2 comunication RRS feed

  • Question

  • We are building an integration in BTS2006R2 using edifact (Orders, Desadv and Invoice) documents, using an schema that we built, every thing works locally, but when we started to send the documents using the built in AS2, our party indicates that the header is not correct, this is the header they are especting:

    Disposition-notification-to: GROC-CHILEAS2
    Disposition-notification-options: signed-receipt-protocol=optional, pkcs7-signature; signed-receipt-micalg=optional, sha1
    AS2-To: KEYAS2
    AS2-Version: 1.1
    Message-ID: <20748649.1206643046430.JavaMail.xshoewis54a@hoewis54>
    Content-Type: application/pkcs7-mime; smime-type=enveloped-data; name=smime.p7m
    Content-Disposition: attachment; filename=smime.p7m

    but this is what they are getting from us:

    Content-Type: application/pkcs7-mime; smime-type=enveloped-data; name="smime.p7m"
    Mime-Version: 1.0
    Content-Length: 10151

    as we are not sending the message-id they can't process it.

    Any ideas on what we are doing wrong?


    Wednesday, April 9, 2008 6:35 PM

All replies

  • Claudio,


    Have you set the AS2-From and AS2-To properties in the parties AS2 Properties - Party as AS2 Message Receiver? On their party profile, you should have your AS2 identifier as AS2-From, and their AS2 identifier as AS2-To.



    Thursday, April 24, 2008 9:29 PM
  • There was a firewall that was filtering the content of the header, now the header is reaching their server, but, we can't change the content type, these is the header we send

    Content-Type: multipart/signed; protocol="application/pkcs7-signature";

    and they need

    Content-Type: application/pkcs7-mime; smime-type=enveloped-data; name=smime.p7m

    Do you now how to change these data?

    thanks for your response
    Friday, April 25, 2008 4:00 PM
  • Claudio,


    In my experience, arranging AS2 between trading partners is done more on terms of agreeing on things like what type of encryption is to be used, whether or not the message will be compressed, how messages will be signed, and whether or not MDN (message disposition notification) will be used. These settings will generally determine the content of the AS2 header.


    With that said, there is a Default Content Type setting just above the AS2-From and AS2-To settings I referenced earlier. You can try this setting to see if it works for you.






    Friday, April 25, 2008 5:07 PM

    If your settings are to encrypt and sign (or compressed and sign), the encrypted(/compressed) data is signed and it becomes a multi-part msg and one part of the multi-part message is the 'encrypted' msg with the smime-type as 'enveloped-data' and the part would the signature.


    If they require only one header - the one u are looking for then encryption must be the last thing to be done. Or just turn off signing if that is not what the partner wants!


    Your prob may have been solved by now - this post is quite old. Else ping again.



    Monday, June 9, 2008 6:20 AM