DBA Implementation

This page will contain lessons learned, tips and tricks on implementing the solution for Doing Business Abroad.

Tips for new Member States implementing and using the DE4A Connector

• Use connectathons as early as possible to share experiences in the setup and resolve issues together.
• Use the publicly available playground and instructions to set up and configure the national DE4A Connector.
• Configure the DE4A Connector using a less strict setup for cryptographic validation, to to sort out connectivity issues. Trying to solve issues with strict cryptographic adherence is difficult as the encryption can cause errors, that are not related to the actual functionality and connectivity

Tips for new Member States implementing and using eIDAS and validating the mandates of representatives

... to be added ...

Establishing connections

The DBA pilot is establishing and testing connections between participating Member States, using testcases and connectathons. During specific timeslots, experts of 2 (or more) countries join with technical experts of the DE4A program. The meetings are online, and focus on establishing the connection between DE4A Connectors or eIDAS nodes. Pre-defined testcases are used to collect necessary proof that the connection is functioning correct. Any last-minute errors are being resolved immediately (if possible).

DE4A Connector

Process

For establishing connections between DE4A Conectorsof participating Member States the following steps are performed:

• Preparation
  • collecting necessary information for configuration of the common components.
• Local testing
  • setting up the national DE4A Connector and connecting this to a DE4A Connector in the DE4A playground.
• Conectivity testing
  • testing a full chain of components, using a Mocked DE, the national DE4A Connector (acting as a DT or DR), the playground DE4A Connector (acting as a DR or DT) and a Mocked DE.
• Connectathon
  • testing a full chain of components, using a Mocked DE, one national DE4A Connector (acting as a DT or DR), another national DE4A Connector (acting as a DR or DT) and a Mocked DO (Milestone 2 and 3)
  • testing a full chain of components, using a real DE, one national DE4A Connector (acting as a DT or DR), another national DE4A Connector (acting as a DR or DT) and a real DO (Milestone 4)

During the OOP TS connectathons, these test cases and preparations are being used / executed.

File:20210615 Test cases DE4A cross-border.xlsx

Planning DE4A Connector connectathons

For each milestone, connectathons are scheduled according to the tables below.

DE4A Connector Milestone 2 and 3 (Only with DE4A Connectors)

		DT
		AT	NL	RO	SE
DR	AT		Probably September	Probably September	August 30th / September 3rd
	NL	Probably September		June 1st/4th (to be completed July14th/16th)	August 30th / September 3rd
	RO	Probably September	June 1st/4th (to be completed July14th/16th)		August 30th / September 3rd
	SE	August 30th / September 3rd	August 30th / September 3rd	August 30th / September 3rd

DE4A Connector Milestone 4 (Also with DO and DE)

		DT
		AT	NL	RO	SE
DR	AT		October / November	October / November	October / November
	NL	October / November		October / November	October / November
	RO	October / November	October / November		October / November
	SE	October / November	October / November	October / November

eIDAS nodes

Connections between eIDAS nodes are established using existing eIDAS procedures and are scheduled in these timeslots:

eIDAS Milestone 1

	Proxy
		AT	NL	RO	SE
Connector	AT		July 5th/9th	July 12th/16th (likely later)	(will be rescheduled)
	NL	July 5th/9th (likely later)		July 12th/16th	(will be rescheduled)
	RO	July 12th/16th (likely later)	July 12th/16th		(will be rescheduled)
	SE	(will be rescheduled)	(will be rescheduled)	(will be rescheduled)

Status of connections

The current status of participating Member States having established connections is displayed in the tables below:

eIDAS Milestone 1: Connecting eIDAS proxies and connectors

	Proxy
		AT	NL	RO	SE
Connector	AT
	NL
	RO
	SE