AS2 Connector, MDN get failure with in .json, but in .mdn file not error

Question

Hi All,

We are sending a file via AS2 connector, and we have a MDN reply in the .json file with the following info:

```
{
  "failure-code": "INSUFFICENT_MESSAGE_SECURITY_UNENCRYPTED",
  "mdn-subject": "Message Disposition Notification",
  "status-code": "FAILED",
  "mdn-message-id": "XXXXX.2024-09-23.16.08.16@5r6UxvKDENuQSQOXXXXXXXXX\u003d",
  "as2-to": "00000000DUST",
  "failure-message": "**Message with ID \XXXXX.2024-09-23.16.08.16@5r6UxvKDENuQSQOXXXXXXXXX\u003d\u0027 contains an unencrypted payload. Encryption is required**.",
  "as2-from": "95331311FMAI",
  "as2-message-id": "5b4f4a39-d463-4082-8340-XXXXXX@XXXXXXXXX",
  "transfer-id": "XXXXXX-1cba-4ad3-95c3-XXXXXX",
  "connector-id": "c-XXXXXXXXXXXXX",
  "file-path": "/XXXXXXX/upload/XXXXXXXXX",
  "timestamp": "2024-09-23T20:08:17.679173436Z"
}
```

Not sure if the error is from my end or partners. 
Can anyone help me?

Thank you

AWS Transfer Family · Answer

Hello, this is an error message sent from your partner. They were unable to process you message because it was unencrypted. We can assume that your partner only accepts encrypted AS2 messages based on this MDN response.

Could you confirm the configuration details of your AS2 connector? Is your encryption algorithm set to ```NONE```? If so, we recommend that you update your connector by choosing one of the supported encryption algorithm options found [here](https://docs.aws.amazon.com/transfer/latest/APIReference/API_As2ConnectorConfig.html#TransferFamily-Type-As2ConnectorConfig-EncryptionAlgorithm) (```AES128_CBC```, ```AES192_CBC```, ```AES256_CBC```, or ```DES_EDE3_CBC```) and trying to send the message again.

Before choosing an encryption algorithm, make sure to ask your partner which algorithm(s) they support. If you send a message with an encryption algorithm that you partner does not support, you will receive another error.

MatiasH · Answer

HI thank you for your replay.

Actually I can not select NONE in Encryption algorithm I set DES_EDE3_CBC, as my partner requested. I try sending message with AES128_CBC, AES192_CBC, AES256_CBC, but I have the same error message.

When I don't use MDN the message is sent to my partner and they can decrypted with out a problem.

That's why I was thanking this is maybe a AWS message and not my partner failure message.

AWS Transfer Family · Answer

Hi, thank you for the clarification. Could you confirm whether your customer supports 112 or 168 bit keys for 3DES? Also, are you able to submit a support case so the Transfer Family engineering team can investigate the issue?

AS2 Connector, MDN get failure with in .json, but in .mdn file not error

Add your answer

Relevant content