Overview of the sedex Client¶

The sedex Client is a software that sedex participants install in their data center. It is the endpoint of the sedex system and allows business applications to send and receive sedex messages.

Core functionalities of the sedex Client¶

The sedex Client provides the following core functionalities:

Secure asynchronous messaging¶

Secure transport of sensitive data
Sender-side message encryption for targeted recipients; only the recipients can decrypt the message (known as end-to-end security)
Message content integrity check by means of digital signatures
Reliable transport for very large data files (up to 10 GB, compressed or uncompressed)
Sending/receiving of messages is non-repudiable
Audit trail of the message exchange (envelope information only)

sedex Webservice Proxy¶

Offers local access to defined remote Web services
Uses the participant’s sedex certificate for the secure SSL/TLS channel to the target Web service
Enables the Webservice provider to identify and authorize the caller

Three components of the sedex Client¶

The sedex Client consists of three separate components (processes) which are running:

The sedex Client’s three components (processes)

1. sedex Controller¶

The process that controls and monitors the sedex Client’s two other processes (see the next two points). For example, the sedex Controller is able to control the sedex Client's processes locally and/or remotely and to perform automatic updates of the sedex Client software and its certificates.

2. sedex Adapter¶

The sedex Client’s main process, offering the functions that enable the secure and reliable exchange of asynchronous messages on the sedex Client side.

3. sedex Webservice Proxy (WS-Proxy) / REST API for Messaging¶

An optional process that offers a secure proxy for SOAP and RESTful Webservices and the new rest-based messaging api. It is not needed for file-based sedex message exchange.