Changes
<-- Terms and conditions



Changes

Version 1.3.0

Main changes

  • The web interface UI has been completely rewritten, and has received additional functionality.
  • It is now possible to configure MFA using TOTP. You can configure it on the user settings page. Enabling MFA does not change access using the API key, but be aware that it does change the obtain_jwt_token API call. Please see API Authentication for the new process. You can set up MFA for testing and production separately.
  • Participants that are the target of SMP Redirects from other SMPs must now explicitely be configured
  • Participants have a new text field ’note’ which is not used in their publication, but can be used for internal management, such as an internal reference number, associated client account, or other internal documentation hints. The search filter on the participant pages includes a search on the notes field.
  • Changing endpoint or endpoint profile details is now much faster, especially when there are many configured participants for the endpoint.

Please note that this update contains some minor API changes. With the exception of the JWT login method if MFA is enabled, these changes are backwards compatible: they only contain additional model fields that are optional, and additional query parameters in search pages.

Web interface

  • The web interface has a new layout and a different way of communicating with the backend
  • The user settings page tabs for primary accounts have been moved to separate pages ‘Account & billing’ and ‘Users’
  • The table on the participants overview page now shows the participants endpoint profile (if any)
  • You can now filter on endpoint, endpoint profile, or redirect directly on the participants overview page
  • The participant create/edit page has a new checkbox ‘publish as redirect target’, which must be enabled if the participant is the target of a redirect from a primary SMP. If this is not enabled, the participant’s XML data is not published.
  • The participant create/edit page has a new text field ’note’. The value of this field is shown in the table of the participants overview page.
  • The endpoint details page now also shows the ’not valid before’ and ’not valid after’ details of the configured certificate
  • There is a new page ‘document types’, which shows all the document types that are configured for all your users, either directly, through an endpoint profile, or for a redirect. The overview also shows the number of participants that have this document type enabled. By clicking on the table row, you go to the participants list, filtered for that document type. Note that this particular filter cannot be set from the participants view itself, you must go through the document types page.

API

  • Participant create/edit/details endpoints have a new boolean field redirect_target_activation, which is to be set to true if the participant is the target of a redirect from a different SMP
  • Participant create/edit/details endpoints have a new textfield note, which is not used in publication, but can be used for internal management purposes.
  • If MFA is enabled, the ‘obtain_jwt_token’ endpoint no longer directly returns the session object; instead, it returns an ephemeral token that must be submitted together with the TOTP code to a new endpoint. If correct, this endpoint returns the session values. If MFA is not enabled, the process remains the same, and the session credentials are returned instantly.
  • The certificate_parse endpoint now also includes not_valid_before and not_valid_after fields

Version 1.2.2:

  • The participant count links for endpoints, endpoint profiles, and redirects now link to the participant view of the participants filtered by that endpoint, profile, or redirect.
  • The participant API endpoint has additional filter options to provide this functionality

Version 1.2.1:

  • The fields ‘contacts’, ‘website_uris’, and ‘additional_identifiers’ are now optional when creating/updating business cards. They were semi-optional already, in that you could just use empty lists, but with this change you can leave them out altogether.

Version 1.2.0:

  • Improved the way the SMP communicates with the Peppol Directory. Changes will still not be immediate (that is up to the directory), but it will regularly check and re-send the update signal after a change of a participant.
  • Assorted small fixes in the web UI:
    • Business cards name languages now use the official ISO-639 set
    • The signed XML data no longer adds the C14N Transform element, as per SMP specification (C14N is still applied)

Version 1.1.0:

List of changes

  • Added support for redirect configuration in the API and frontend
  • Updated base URL for API

Redirect support

While the backend already had support for SMP Redirects, it could only be configured by the administrator. You can now manage redirects for your Participants directly, through either the web interface or the API.

Configuring redirects in the web interface is documented on the Managing Redirects page.

As for the API, there are two new general endpoints:

  • /api/v1/redirects for global configuration of the redirects themselves
  • /api/v1/participants/<id>/redirects to assign redirects to participant/document types

A full list of endpoints, methods, and datastructures can be found in the API redoc page

Renamed the base API endpoint.

Originally, the base API endpoint was versioned as ‘1.0’, e.g. /api/smp/1.0. Since minor releases such as 1.1 should be backwards compatible, we have decided to rename it to /api/smp/v1 instead.

It is not required to update your configured client settings, as 1.0 has been kept as an alias for your convenience, but we do recommend to update to /api/smp/v1.

Version 1.0.0:

Initial release.