Daniel.forsberg: Created page with "The task of a Service Metadata Publisher (SMP) is to create the link between the technical identifiers and the effective endpoint URL to exchange messages with. Additionally,..."

2021-08-30T11:12:10Z

Created page with "The task of a Service Metadata Publisher (SMP) is to create the link between the technical identifiers and the effective endpoint URL to exchange messages with. Additionally,..."

New page

The task of a Service Metadata Publisher (SMP) is to create the link between the technical identifiers
and the effective endpoint URL to exchange messages with. Additionally, it provides X.509
certificates that will be used to encrypt messages for a specific recipient. Each participant has a list of
so called “Endpoints” that are uniquely identified by a combination of a document type identifier, a
process identifier and a transport profile. An SMP makes it possible for two parties in the domain to
exchange documents with dynamic discovery and utilizing the 4 Corner Model used for eDelivery
within the DE4A project.

For the CEF documentation on SMP please see [https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/SMP+specifications CEF]

The SMP deployed within the DE4A project at the time of this writing is the [https://github.com/phax/phoss-smp phoss] SMP and the documentation is [https://github.com/phax/phoss-smp/wiki here]

SMP - Revision history

Daniel.forsberg: Created page with "The task of a Service Metadata Publisher (SMP) is to create the link between the technical identifiers and the effective endpoint URL to exchange messages with. Additionally,..."