Difference between revisions of "MA implementation"
| Line 199: | Line 199: | ||
{| class="wikitable" | {| class="wikitable" | ||
|+ | |+ | ||
| − | ! colspan="4" | Use case [ | + | ! colspan="4" | Use case [Change of Domicile Address] |
|- | |- | ||
| colspan="2" |'''Data provider country''' | | colspan="2" |'''Data provider country''' | ||
| Line 209: | Line 209: | ||
|'''Status in this use case''' | |'''Status in this use case''' | ||
|- | |- | ||
| − | |[ | + | |[LU] |
|Pick whichever one applies: | |Pick whichever one applies: | ||
''[not active yet] [issuing fake data] [issuing real data]'' | ''[not active yet] [issuing fake data] [issuing real data]'' | ||
Revision as of 11:00, 20 September 2022
This page will contain lessons learned, tips and tricks on implementing the solution for Moving Abroad. Moving abroad uses only one iteration covering the functionality of both the planned first and second iteration also, the planning and status of establishing connections between participating Member States are presented.
Contents
- Tips for new Member States implementing and using the DE4A Connector
- Establishing connections
- DE4A Connector
- Process
- Planning DE4A Connector Connectathons
- eIDAS nodes
- Status of connections
- Legal issues encountered
- 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"
DE4A Connector Connectathon results
For each milestone, Connectathons are scheduled according to the tables below.
Status of connections second iteration (continuously updated)
The current status of participating Member States having established connections is displayed in the tables below:
| Proxy | ||||||
|---|---|---|---|---|---|---|
| ES | PT | LU | SL | RO | ||
| Connector | ES | |||||
| PT | ||||||
| LU | ||||||
| SL | ||||||
| RO | ||||||
| DE4A Connector acting as DT | ||||||
|---|---|---|---|---|---|---|
| ES | PT | LU | SL | |||
| DE4A Connector
acting as DR |
ES | |||||
| PT | ||||||
| LU | ||||||
| SL | ||||||
| RO | ||||||
| MS acting as DP | ||||||
|---|---|---|---|---|---|---|
| ES | PT | LU | SL | RO | ||
| MS
acting as DC |
ES | |||||
| PT | ||||||
| LU | ||||||
| SL | ||||||
| RO | ||||||
MA Use Case issues identified
The template below was created to keep track of the status of use cases, including to register any legal issues encountered and possible solutions.
The template should be applied at the use case level, registering the status for each country. Sections in italics should be updated. Use one line per Member State.
Where inputs don't fit into the template (too long or complex), pilot participants can add additional notes below the table.
| Use case [Change of Domicile Address] | |||
|---|---|---|---|
| Data provider country | Data evaluator country | ||
| Member State name | Status in this use case | Member State name | Status in this use case |
| [LU] | Pick whichever one applies:
[not active yet] [issuing fake data] [issuing real data] |
[Member State name] | Pick whichever one applies:
[not active yet] [receiving fake data] [receiving real data] |
| [Member State name] | Pick whichever one applies:
[not active yet] [issuing fake data] [issuing real data] |
[Member State name] | |
| Identified risks / problems / incidents | Implemented solutions or plan (note: use the same line as the risk/problem/incident, so
that the solution/plan matches the risk/problem/incident next to it) | ||
| [Member State(s) name(s)] | Describe: dd/mm/yyyy, [description of the risk/problem/incident | Describe: dd/mm/yyyy, [description of the solution or plan] | |
Additional notes:
[Provide any additional information that's required to describe the status of the use case, if applicable. Copy and paste to add a new issue]
Where inputs don't fit into the template (too long or complex), pilot participants can add additional notes below the table.
| Use case [name] | |||
|---|---|---|---|
| Data provider country | Data evaluator country | ||
| Member State name | Status in this use case | Member State name | Status in this use case |
| [Member State name] | Pick whichever one applies:
[not active yet] [issuing fake data] [issuing real data] |
[Member State name] | Pick whichever one applies:
[not active yet] [receiving fake data] [receiving real data] |
| [Member State name] | Pick whichever one applies:
[not active yet] [issuing fake data] [issuing real data] |
[Member State name] | |
| Identified risks / problems / incidents | Implemented solutions or plan (note: use the same line as the risk/problem/incident, so
that the solution/plan matches the risk/problem/incident next to it) | ||
| [Member State(s) name(s)] | Describe: dd/mm/yyyy, [description of the risk/problem/incident | Describe: dd/mm/yyyy, [description of the solution or plan] | |
Additional notes:
[Provide any additional information that's required to describe the status of the use case, if applicable. Copy and paste to add a new issue]