New versions of X-Road core are published three times a year based on a fixed release schedule. X-Road technical release roadmap for 2019 is presented below.
N.B. Changes in prioritization may cause roadmap for 2019 to change - new features may be introduced and/or implementation of current features may be postponed. X-Road product backlog is prioritized either by Advisory Group or Working Group depending on the development item.
Summary of changes included in version 6.20.0.
Support for Ubuntu 18.04 LTS.
Central Server, Security Server and Configuration Proxy can be migrated from Ubuntu 14.04 LTS to the latest Ubuntu 18.04 LTS version.
Ubuntu 14.04 LTS will quit receiving maintenance updates in Q2/2019 which is why migration is required.
Ubuntu 18.04 LTS support includes installation packages, and instructions for fresh install and migration from Ubuntu 14.
Security Server provides built-in support for Finnish data classification system level ST IV.
The default security configuration has been updated according to the Finnish Communications Regulatory Authority's requirements.
Messagelog time-stamping has been improved so that messagelog records are always verifiable regardless of the number of processed messages and Security Server’s load.
Security Server's security and maintainability is improved replacing customised and outdated 3rd party components with the latest off-the-shelf versions of the components.
In addition, maintainability is improved removing unsupported features and dead code from the codebase.
Summary of changes included in version 6.21.0.
Security Server provides support for consuming and producing both SOAP and REST services.
REST-based systems can be integrated to X-Road without technical changes and an additional adapter service component.
REST support is not limited to just JSON and XML messages as Security Server does not set any restrictions to the content type of the payload that is transferred between a service consumer and a service provider.
Consuming and producing SOAP services remains supported and no changes are required to existing SOAP based service consumers and producers.
X-Road onboarding process is streamlined enabling automatic approval of registration requests of new X-Road member organizations and information systems.
X-Road operator may choose between automatic and manual approval of registration requests within an X-Road ecosystem.
Automatic approval speeds up the registration process and reduces the daily management tasks of the X-Road operator.
Security Server performance is optimised to make message processing faster. (not implemented in v6.21.0)
Optimisation speeds up messagelog archival process and optimises Security Server's resource usage. (not implemented in v6.21.0)
Security Server is able to automatically adjust the amount of hardware resources allocated to it. (not implemented in v6.21.0)
Standalone Security Server is a special version of Security Server that is ready-to-use in minutes without the normal Security Server installation, configuration and registration process.
Standalone Security Server is meant for testing purposes in X-Road service development and it cannot communicate with other Security Servers.
Standalone Security Server is targeted especially to developers and organizations that are developing services to be published via X-Road.
Summary of changes included in version 6.22.0.
Support for publishing REST services to X-Road using API descriptions and support for more fine grained access rights managements of REST services.
Additional improvements based on user feedback received from version 6.21.0.
New user interface provides improved user experience (UX) for Central Server and Security Server administrators.
New intuitive user interface makes taking care of administrative tasks easier and supports streamlining the onboarding process of new X-Road members.
Common maintenance and configuration tasks can be automated using the administrator API.
Maintaining and operating multiple Security Servers can be done more efficiently as configuration and maintenance tasks require less manual work.
Better support for running Security Server on cloud platforms enables use of different cloud services together with Security Server, e.g. cloud HSMs and auto scaling.
Cloud services can be used to reduce administrative tasks of operating Security Server, optimise infrastructure costs and increase availability.
Security Server administrators can define preferred order for OCSP and TSA services.
Free or low cost service providers can be defined as primary service providers which are used by default.
Service providers with lower priority are used only if primary services are not available. In case OCSP and/or TSA are paid services this helps to lower Security Server operational costs.
Support for enhanced security configuration in clustered time-stamping services is added.
A cluster may contain multiple time-stamping service instances that do not use shared a certificate and a private key which increases the security of the service.
Link to release notes will be added once the version has been released.