AS4.NET is an open-source application that implements the OASIS AS4 specification. It supports both the e-SENS e-Delivery and the EESSI AS4 Messaging profile as an ebMS endpoint.
Since version v3.0.0, AS4.NET can also act as an intermediary MSH (i-MSH) with message forwarding support and MEP bridging.
The component has been conformance tested against the e-SENS eDelivery specifications.
Testing against the EESSI AS4 Messaging Profile has also been conducted.
AS4.NET is interoperable with multiple other AS4 gateway providers; AS4.NET has undergone performance and interop-tests against Holodeck B2B, RSSBus, Domibus, Flame Message Server and IBM B2B.
AS4.NET can be downloaded from the following locations:
- AS4.NET v4.0.0
- AS4.NET v3.1.0
- AS4.NET v3.0.0
- AS4.NET v2.0.1
- AS4.NET v2.0.0
- AS4.NET v1.1.0
- AS4.NET v1.0.0
A configuration- and usermanual can be found online.
- One-Way/Push message exchange pattern
- XML based configuration
- XML based PMode configuration
- Dynamic PMode override
- Multiple submit, notify and deliver agents
- FILE based receivers and senders
- Signing and encryption using WS-Security
- AS4 Compression
- AS4 Reception Awareness and Retry
- AS4 Duplicate Detection and Elimination
- Submit, deliver and notify via HTTP protocol
- Submit and deliver attachments via HTTP protocol
- One-Way/Pull pattern as initiator
- Support for sub channels in One-Way/Pull pattern
- Support for multi-hop AS4 profile
- Support for TLS client certificates
- Performance tuning for large messages, up to 2GB
- Performance tuning for high volume processing
- Web interface for configuration
- Web interface for monitoring
- Web interface for user management
- Web interface for testing
- One-Way/Pull pattern as responder
- Support for sub-channels
- Support for message forwarding
- Support for MEP bridging
- Support for PullRequest authorization
- Support for SMP/SML dynamic discovery
- Support for TLS server side
- Continued performance tuning for large messages, up to 3GB
- Continued performance tuning for high volume processing
- Improvements to the internal messaging engine
- Configurable payload naming when delivering on filesystem
- Continued performance tuning for large messages and high volume processing
- Intermediary MSH functionality with message forwarding including MEP bridging support
- Static Submit support
- Possibility to run the AS4.NET MSH as a Windows Service
- Improved Dynamic Discovery implementation
- Dynamic Forwarding support
- Improved high availability support
- Support for Non-Repudiation of Receipt verification
- Support for automatic Message Cleanup
- Optionally allow that a message is signed with a certificate coming from an unknown CA authority when verifying message signatures
- Web interface for SMP Routing Configuration
- Improvements in the web interface for configuration
- Improvements to the internal messaging engine
- Retry functionality for deliver operation
- Retry functionality for notify operation
- Static Receive support
- Improvements in the web interface for configuration
- Improvements in the internal messaging engine
- Support for the OASIS BDX dynamic discovery profile
- Support for sending response signal messages via reliable piggybacking in a pull receive scenario
- Allow the AS4.NET Windows Service MSH to be installed via an MSI
- Control the AS4.NET Windows Service MSH via a system tray application
- Improved Receiving PMode matching proces when multiple from-parties / to-parties are specified in the AS4 Message or in the Receiving PMode
- Allow dynamic discovery based on the sender information in the SubmitMessage or in case of a forwarding scenario on the sender information in the AS4 Message
- Support for internal journal logging to track down operations executed on the message (compress/decompress, signing/verify, encrypt/decrypt)
- Support for receiving bundled message units
- Configurable submit payload retrieval path location
- Configurable pull authorization map path location
- Improvements in the web interface for pmode and agents configuration
- Improvements to the internal messaging engine
This version doesn't support Sending PModes anymore as a way to respond to AS4 messages but uses the Receiving PMode for this. Please update your Receiving PModes, for more information see: Remove Sending PMode as responding PMode.
The following third party libraries are used by AS4.NET runtime:
- BouncyCastle (MIT License)
- FluentValidation (Apache 2)
- Mimekit (MIT License)
- Nlog (BSD License)
- Polly (BSD License)
- SQLite (Public Domain)
- Remotion (Apache 2)
This software is licensed under the EUPL License v1.1.