Moving Abroad Pilot
The Moving Abroad pilot of the DE4A project, implements eProcedures for moving and living abroad (MA) in Luxembourg, Portugal, Romania, Slovenia and Spain. It improves currently available cross-border procedures by implementing the Once Only Principle (OOP). Piloting solutions to these highly complex processes are an important step in breaking down barriers in the European single market. In the end people should be able to move to other Member State as easy as they do nationally. The MA pilot highly values experience from piloting real eProcedures.
The MA pilot addresses some of the most important research questions for successfully implementing the SDGR and SDGR-related processes. Besides validating the OOP technical System for evidence exchange in real use cases it goes beyond the minimum service to support people being more mobile. Furthermore, the MA pilot pilots several SDGR-specific and related functions, like explicit request and preview, canonical evidence and record matching.
The 4.10 deliverable specifies the design of the MA pilot and provides a plan for managing all activities in the upcoming two phases: customization & integration phase and pilot running phase.
Sections
Use Case "Request Address Change" (MA UC1)
Use Case "Request an Extract or Copy of a Civil State Certificate" (MA UC2)
Use Case "Request Pension Information - Claim Pension" (MA UC3)
MA Implementation
This page will contain lessons learned, tips and tricks on implementing the solution for Moving Abroad. Also, the planning and status of establishing connections between participating Member States is presented.
Contents
- 1 Tips for new Member States implementing and using the DE4A Connector
- 2 Establishing connections
- 3.1 DE4A Connector
- 3.1.1 Process
- 3.1.2 Planning DE4A Connector Connectathons
- 3.2 eIDAS nodes
- 3.3 Status of connections
- 3.1 DE4A Connector
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 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
Establishing connections
The MA 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 Connectors of 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.
- Connectivity 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 DO.
- 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 Connectathons, test cases and preparations that are being used / executed are found in the MA-OwnCloudfolder "Connectathon"
Planning DE4A Connector Connectathons
For each milestone, Connectathons are scheduled according to the tables below.
DT | |||||
---|---|---|---|---|---|
ES | PT | LU | SI | ||
DR | ES | N/A | N/A | N/A | |
PT | N/A | N/A | N/A | ||
LU | Pass | Pass | Pass | ||
SI | N/A | N/A | N/A |
MS acting as DP | |||||
---|---|---|---|---|---|
ES | PT | LU | SL | ||
MS
acting as DC |
ES | ||||
PT | |||||
LU | |||||
SL |
eIDAS nodes
Connections between eIDAS nodes are established using existing eIDAS procedures and are scheduled in these timeslots:
Proxy | |||||
---|---|---|---|---|---|
ES | PT | LU | SL | ||
Connector | ES | ||||
PT | |||||
LU | |||||
SL |
Status of connections
The current status of participating Member States having established connections is displayed in the tables below:
Proxy | |||||
---|---|---|---|---|---|
ES | PT | LU | SL | ||
Connector | ES | ||||
PT | |||||
LU | |||||
SL |
DE4A Connector acting as DT | |||||
---|---|---|---|---|---|
ES | PT | LU | SL | ||
DE4A Connector
acting as DR |
ES | ||||
PT | |||||
LU | |||||
SL |
MS acting as DP | |||||
---|---|---|---|---|---|
ES | PT | LU | SL | ||
MS
acting as DC |
ES | ||||
PT | |||||
LU | |||||
SL |
Green = Connection established
Yellow = Connection partlially established (issues remaining to be solved)
Red = Connection not established yet