Text size

Spacing

Contrast
Settings

 

Transition to X-Road version 6

On 2 November 2015, transition was launched to X-Road version 6. The transition is expected to be completed by the end of 2017.

If your organization has difficulties transferring to X-Road version 6 and changing platform is not possible during 2017, please contact RIA (help at ria dot ee) as soon as possible.

Information and deadlines

Information from institutions who have X-Road version 6 services in different environments can be found at http://x-road.eu/allmethods/. It’s updated once a day. 

X-road version 5 environments closing dates:

  • production on  31.12.2017
  • test and development on 31.09.2017

The situation today:

  • Data is exchanged on X-Road version 6 according to Public Information Act,
  • Cerificates for X-road version 5 development and test environment are not being issued anymore.
  • Cerificates for X-road version 5 production environment are issued only if the insitution submits a schedule for the transition to X-Road 6 or if, for some reason, the necessary data services are not yet usable on X-Road v6 environments.
  • RIA has created preconditions to enable the members to introduce version 6 (in development, test as well as production environment):

Why did the transition occur?

The purpose of X-Road is to ensure the integrity of information during information exchange between organizations. The purpose of X-Road version 6 is to change the former security plan of X-Road and resolve ensuring the integrity of messages transmitted via X-Road by using a qualified digital stamp (e-stamp). At the same time, in order to preserve the security of X-Road, legacy or programme code that has not withstood the test of time needs to be eliminated (no legacy policy). The long-term reason is the need to ensure compliance of X-Road data exchange with the Digital Signatures Act. Therefore, the existing method for ensuring integrity of the X-Road must be changed so that the e-stamp certificates of a member must be issued by qualified providers of trust services. In addition, the e-stamp certificates need to be connected with secure signature-creation devices.

The following changes are involved in eliminating legacy and organizing the member management system:

  1. Changes in the transport protocol of the X-Road, or in methods, how security services process and exchange messages.
  2. Changes in the X-Road message protocol, i.e., what kind of structure do the messages have that security servers exchange.

When ensuring a secure data exchange, it is important that holders of the digital stamp (e-stamp) certificate or legal persons can be the parties that bear mutual liability. That means that, in version 6, the X-Road members are legal persons. With the same certificate, the X-Road members are able to both use and provide services.

It must be highlighted that the message protocol describes the physical structure of messages moving between the information system (interface component) and the security server, and can be observed independently from the X-Road security server. The message protocol version does not, therefore, comply with the X-Road (security and central server) version. Every X-Road version supports one or more message protocol(s). The way the security server processes a message (incl. e-stamps and logs), depends on the X-Road security server version and not on the message protocol version.

How did the transition take place?

The time frame of the transition is established by the Directive No 1.1-2/16-146 of the Director-General of RIA of 1 November 2016 (in Estonian, .pdf, 66 KB)

What changed?

Short overview of changes (in Estonian, .pdf, 85 KB)

The main instructions about the transition

 


Did you get the answer to your question?

Added 01.03.2016
Updated 07.07.2017

Back to page "For a member of X-Road"