Decode AS2 messages with Azure Logic Apps and Enterprise Integration Pack
To establish security and reliability while transmitting messages, use the Decode AS2 message connector. This connector provides digital signing, decryption, and acknowledgements through Message Disposition Notifications (MDN).
Before you start
Here's the items you need:
- An Azure account; you can create a free account
- An integration account that's already defined and associated with your Azure subscription. You must have an integration account to use the Decode AS2 message connector.
- At least two partners that are already defined in your integration account
- An AS2 agreement that's already defined in your integration account
Decode AS2 messages
The Decode AS2 message connector doesn't have triggers, so you must add a trigger for starting your logic app, like a Request trigger. In the Logic App Designer, add a trigger, and then add an action to your logic app.
In the search box, enter "AS2" for your filter. Select AS2 - Decode AS2 message.
If you didn't previously create any connections to your integration account, you're prompted to create that connection now. Name your connection, and select the integration account that you want to connect.
Properties with an asterisk are required.
Property Details Connection Name * Enter any name for your connection. Integration Account * Enter a name for your integration account. Make sure that your integration account and logic app are in the same Azure location.
When you're done, your connection details should look similar to this example. To finish creating your connection, choose Create.
After your connection is created, as shown in this example, select Body and Headers from the Request outputs.
AS2 decoder details
The Decode AS2 connector performs these tasks:
- Processes AS2/HTTP headers
- Verifies the signature (if configured)
- Decrypts the messages (if configured)
- Decompresses the message (if configured)
- Check and disallow message ID duplicates (if configured)
- Reconciles a received MDN with the original outbound message
- Updates and correlates records in the non-repudiation database
- Writes records for AS2 status reporting
- The output payload contents are base64 encoded
- Determines whether an MDN is required, and whether the MDN should be synchronous or asynchronous based on configuration in AS2 agreement
- Generates a synchronous or asynchronous MDN (based on agreement configurations)
- Sets the correlation tokens and properties on the MDN
If you use Azure Key Vault for certificate management, make sure that you configure the keys to permit the Decrypt operation. Otherwise, the AS2 Decode will fail.
Try this sample
To try deploying a fully operational logic app and sample AS2 scenario, see the AS2 logic app template and scenario.
View the swagger
See the swagger details.