SMP v3.0 RC1

This page collects the resources for Service Metadata Publisher version 3.0-RC1, released in February 2017. 
 

Description

We are happy to announce the first release candidate of the sample implementation of the eDelivery Service Metadata Publisher (SMP).

This release is conformant with the e-SENS SMP profile based on the OASIS Service Metadata Publishing (BDX SMP) specifications. It is a candidate version that is potentially ready to be released unless significant bugs emergence as results of the tests executed by the future clients of the service before the release of the final version.

All necessary functionality is available to make the SMP fully operational; i.e. all necessary operations to manage Service Groups (structures that represent a set of services associated with a specific Participant identifier) and their Service Metadata (structures that represent Metadata about a specific electronic service):

• Creation, update and deletion of Service Groups.
• Creation, update and deletion of Service Metadata.
• SML integration.
• Security, including:
• support of https for simple users;
• mutual TLS authentication for administrators of metadata;
• authorisation for administrators' service operations;
• user management;
• data validation;
• data integrity validation.
• Logging.

Migration from 2.2.4 to 3.0-RC1

The previous version v2.2.4 of SMP software component maintained by the European Commission only implemented the PEPPOL SMP specifications.

The new version of the SMP software component is intended to be conformant with the e-SENS SMP profile based on the OASIS Service Metadata Publishing (BDX SMP) specifications.

The two being not fully compatible, no migration from one to another can be performed and is therefore not supported.

Documentation

Release note

Please find below the list of the improvements and limitations.

Improvements and new features

• [EDELIVERY-1799] SMP - Error handling - Include XSD validation for ServiceMetadata
• [EDELIVERY-1794] SMP - Distinguish PUT 200 from 201 responses
• [EDELIVERY-1701] SMP - Error handling - handle errors other than 500 (400, 404, 401, ...)
• [EDELIVERY-505] Allow users with less than administrative permissions to manage their own metadata
• [EDELIVERY-1813] Move the common SML API module
• [EDELIVERY-1773] SMP - Move Auth from J2EE container to application level
• [EDELIVERY-1756] SMP Client | Replace Signature Method RSA_SHA1 by RSA_SHA256
• [EDELIVERY-1709] SMP - 2 way SSL - with Reverse proxy
• [EDELIVERY-1698] SMP - Store whole ServiceMetadata within single CLOB column
• [EDELIVERY-1673] Provide Interface for customizing Signature Implementations
• [EDELIVERY-1633] Update SMP Client for latest bdx-smp  version (201605)
• [EDELIVERY-486] Change SingedServiceMetadata from XMLDSig to XaDES
• [EDELIVERY-485] Usage of extension : MUST NOT vs MAY NOT
• [EDELIVERY-484] Change documents to resources
• [EDELIVERY-479] Use HTTPS instead of HTTP to access SMP for confidentiality reasons
• [EDELIVERY-475] Need for the participants to update themselves their metadata

Solves issues

• [EDELIVERY-1863] Extension content is not fully returned in Get serviceGroup
• [EDELIVERY-1860] Creating serviceMetadata with Admin ServiceGroup fails
• [EDELIVERY-1832] Wrong Signature method
• [EDELIVERY-1830] Redirection request returns http 500
• [EDELIVERY-1828] Error when trying to submit service group with ebCore identifiers
• [EDELIVERY-1781] ContentType in SMP Response is incorrect
• [EDELIVERY-1885] Service Group only saves the first Extension
• [EDELIVERY-1872] Submit serviceMetadata with same transport profile inside the same endpointList succeeds
• [EDELIVERY-1866] SMP - Specify Error response for PUT ServiceMetadata when ServiceGroup does not exist
• [EDELIVERY-1818] SMP - Handling default ports in X-Forwarded-Port
• [EDELIVERY-1700] SMP - Error handling - by default HTTP 500 with error UniqueId
• [EDELIVERY-692] [SMP] Deviations identified during the EXPANDATHON 
• [EDELIVERY-1899] Delete serviceGroup error for non existing data 
• [EDELIVERY-1703] SMP - new SMP roles - store CertificationAuthentication ownership if present
• [EDELIVERY-1699] SMP - Add new endpoints for OASIS specs

Known issues and limitations

• [EDELIVERY-1923]Extension optional elements not present cause 400 response
• [EDELIVERY-1900]Put serviceGroup, ServiceGroup-Owner certificate is not registered gives wrong error code
• [EDELIVERY-1835]Case sensitivity issue for Service Group, Participant and Document identifiers
• [EDELIVERY-1827]Issue with identifiers containing slash "/" character
• [EDELIVERY-1817]ServiceGroup - Bad Request
• [EDELIVERY-1927]Resolve discrepancies between validation rules that are applied for Participant Identifiers' scheme - between SMP and SML