File:Setting up a Service Metadata Publisher for DE4A.pdf

2023-03-07T16:18:50Z

Javier.ferrero:

Getting started guide

2023-03-06T16:25:57Z

Javier.ferrero:

This guide provides a list of steps to be taken by each partner wishing to deploy and join the DE4A infrastructure of iteration 2. There are four main activities: getting eDelivery certificates, setting up an SMP for DE4A, setting up a DE4A Connector and the development and integration of the final participant. There is an additional chapter for those participants who wish to use and integrate with the DE4A Playground.

== 1. Getting eDelivery certificates ==
The DE4A network makes use of the eDelivery components and infrastructure to support the exchange of evidence and messages. There are two [[eDelivery]] components that must be deployed and operated by participants in the DE4A network: an SMP and an AS4 Gateway (also know as Access Point). Both must be configured to use a certificate that conforms to the DE4A PKI, following the Trust Management Model established for the DE4A project. DE4A uses a PKI provided by '''CommisSign-2''', which is the Certificate Authority of the European Commission for eDelivery. Getting the eDelivery certificates is necessary to finish the set up of the SMP and DE4A Connector.

In order to obtain the corresponding certificates, a new partner would need to get in contact with the coordination team of DE4A, who can initiate the process to request new certificates. This process is designed by the Certificate Authority.
== 2. Setting up an SMP for DE4A ==
Within the DE4A network, at least one eDelivery SMP must be deployed per participating country. There can be more than one SMP per country, although only one is needed. Therefore, multiple participants from the same country can use the same SMP provided by the corresponding national entity.

The SMP must be installed, configured and populated with the right information. To install and configure the SMP, the following two documents are of help:
* 2022-04-01 Setting up a Service Metadata Publisher for DE4A.pdf
* 2022-05-02 Configuring the SMP for the IAL.pdf
Once the SMP is set up, the operating entity must populate it with the appropriate information of participants and evidence types that the relevant national DE4A participants are going to request and provide. Each SMP must only store and manage the information related to the participants of the same country as where the SMP is located, so that each country is only responsible for its own information.

=== Governance procedure ===
When populating/updating the information in the SMP, the [[Useful information on pilots and participants]] Wiki page should also be updated to stay aligned. After that, both ATOS (Ana María Piñuela, Alberto Crespo, Javier Presa) / WP5 (Javier Ferrero, Javier Baena, Eduardo Moreno, Hugo Berdón) should also be informed about these changes.

=== TIP ===
What information needs to be added?

Create a service group with your participantID:

* Scheme: '''iso6523-actorid-upis'''
* Identifier value: '''99XX:pt000000026-test-it2'''

For that participant (service group) you need to create an endpoint.

Endpoints will have the Document type ID for the Canonical Evidence Type.

If you are a '''DE''', then you need to register a '''response''' endpoint with the Connector URL endpoint and the certificate.

If you are a '''DO''', then you need to register a '''request''' endpoint with the Connector URL endpoint and the certificate.

[[File:Endpointlist.png|none|thumb|800x800px]]
[[File:Certs.png|none|thumb|800x800px]]
The URL for the Connector must be the base URL, followed by “/phase4"
[[File:Conn.png|none|thumb|803x803px]]

For this example, the endpoint URL should be: <nowiki>https://de4a.simplegob.com/de4a-it2-connector/phase4</nowiki>

== 3. Setting up a DE4A Connector ==
The DE4A Connector is needed to be able to exchange messages with other participants, since the communication is realised via these Connectors.The latest release version of the DE4A Connector is available at the [https://github.com/de4a-wp5/de4a/releases GitHub of WP5]. To install the DE4A Connector, an [[Installation and configuration guide of the DE4A Connector it2]] is available.

== 4. Development and integration of the final participant ==
In DE4A, there are two types of the so-called "final participants": Data Evaluators and Data Owners. These are the entities that request or provide evidence, repectively. Each DE4A participant must develop its own final participant and integrate it with the other components.

In order to understand the common specifications each partner needs to follow to properly exchange messages with the rest of the DE4A components, the following resources are available within the Common specifications section of the WP5 part of the DE4A Wiki:

*[[Common behaviour and interactions between components]]
** Description of the interaction patterns of the second iteration through communication diagrams. Data structures used during exchanges are also described there.
* [[Central IAL interface]]
** Description of the software interface of the Central IAL.
*[[Summary of software interfaces.|Summary of software interfaces]]
** Reference information on the software interfaces of the DE4A components.
*[[DE4A Logs and error messages it2|DE4A Logs and error messages]]
** Updated version for the second iteration of the specification of the common error and logs messages used during exchanges.
Once the Data Evaluator or Data Owner has been developed and deployed, it must be integrated with the DE4A Connector and SMP that will be supporting the communication of that final participant:

* The de-do.json must properly updated to include the endpoint of the new final participant.
* The SMP must also be updated with the participant ID and the evidence that the final participant will request (DE) or provide (DO).

== 5. Integration with the Playground it2 ==
The Playground can only be used in two ways:

* By exchanging messages between the DemoUI and the Mocked DO as the participants involved.
* By using the infrastructure of a partner to act as a Data Consumer or Data Provider.
For the second option, it is mandatory to set up a complete interaction side: either the sender (DC) or the recipient (DP). This means that, in this second iteration, the use of only a DE or a DO to exchange messages via the Playground is not supported.

For example, if a partner wants to send a message from its DE to the Mocked DO, that partner needs to set up the complete infrastructure of a Data Consumer:

* A national SMP available to that partner.
* A DE4A Connector.
* A Data Evaluator.
On the other hand, if a partner wants to receive a message in its DO from the DemoUI, that partner needs to set up the complete infrastructure of a Data Provider:

* A national SMP available to that partner.
* A DE4A Connector.
* A Data Owner.
The Shared SMP cannot be used for participants other than the imaginary ones.

=== URL addresses for the Playground environment ===
The Playground environment has a cross border infrastructure. Data consumer side is deployed at the University of Maribor in Slovenia where the DemoUI is acting as Data Evaluator and the Connector as Data Requestor.

* DemoUI DE - https://de4a-demoui-dev.informatika.uni-mb.si/
* Connector DR - https://de4a-connector-dev.informatika.uni-mb.si/

The Data Provider side is deployed at SGAD in Spain where the Connector is a Data Transferor and the Data Owner is the Mocked DO.

* Connector DT - https://pre-as4gw-dt-de4a.redsara.es/de4a-it2-connector/
* Mocked DO - https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/

A Kafka tracker is available through the following URL: https://de4a.simplegob.com/package-tracker/#!detail

For detailed traceability, these are the topics where each component is logging to Kafka.
{| class="wikitable"
|+KAFKA
!Component
!Topic
|-
|DemoUI
|wp5-demoui-it2
|-
|Connector DR
|log-test
|-
|Connector DT
|de4a
|-
|Mocked DO
|test
|}

Kafka

2023-03-01T09:15:15Z

Javier.ferrero: Initial version

The Apache Kafka instance used in DE4A is an Open-Source distributed event streaming platform. It is used to receive messages from the different services used in the project. The received messages can be viewed online as they are received in the Package Tracker made available for everyone. The main purpose is to be able to quickly see if there are any problems between services and what type of problem (e.g. connection problems) to help pilot partners and developers find those issues. Therefore, the main use case is distributed event logging and not digital traffic reporting where full logs are sent and stored off-site. The reasoning for this is that the Kafka instance on the Aeioros servers is fully open, meaning that anyone can read and write messages on that service. To reduce security risks, the Kafka instance does not store messages sent for extended periods of time, i.e. messages are essentially ephemeral.

The particular configuration used for the DE4A project uses ZooKeeper as the coordinator, Kafka as the message broker and the Package Tracker as the web service configured to consume and display any messages received by the Kafka broker. The Package Tracker can only display "live" messages, i.e. any messages received in the past will never be displayed.

RegRep

2023-03-01T09:13:57Z

Javier.ferrero: Initial version

RegRep is a [http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html data format standard by OASIS]. It adds another layer of abstraction onto XML schema and splits the data into so called “slots”.

The usage of RegRep is very limited to inside the DE4A Connector. Before the main DEA message is send it is wrapped into a thin RegRep wrapper.

== RegRep Evidence Request ==
The RegRep Evidence Request consists of the following slots:

* '''SpecificationIdentifier''' (of type String) – Defines the underlying specification that is implemented. Must contain the value <code>de4a-iem-v2</code>.
* '''IssueDateTime''' (of type DateTime) – Defines the date and time when request was created.
* '''DE4AQuery''' (of type Any) – Contains the main DE4A data model.

The following example code shows a complete DE4A RegRep query.<pre>
<query:QueryRequest xmlns:lcm="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:4.0" xmlns:query="urn:oasis:names:tc:ebxml-regrep:xsd:query:4.0" xmlns:spi="urn:oasis:names:tc:ebxml-regrep:xsd:spi:4.0" xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:4.0" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:4.0" id="fa62b109-b564-4985-a322-afb92e82d906">
<rim:Slot name="SpecificationIdentifier">
 <rim:SlotValue xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="rim:StringValueType">
 <rim:Value>de4a-iem-v2</rim:Value>
 </rim:SlotValue>
</rim:Slot>
<rim:Slot name="IssueDateTime">
 <rim:SlotValue xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="rim:DateTimeValueType">
<rim:Value>2023-01-28T20:10:49.827+01:00</rim:Value>
 </rim:SlotValue>
</rim:Slot>
<query:ResponseOption returnType="LeafClassWithRepositoryItem" />
<query:Query queryDefinition="DE4AQueryIt2">
 <rim:Slot name="DE4AQuery">
 <rim:SlotValue xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="rim:AnyValueType">
 
 </rim:SlotValue>
 </rim:Slot>
</query:Query>
</query:QueryRequest>
</pre>

== RegRep Evidence Response ==
The RegRep Evidence Response consists of the following slots:

* '''SpecificationIdentifier''' (of type String) – Defines the underlying specification that is implemented. Must contain the value <code>de4a-iem-v2</code>.
* '''IssueDateTime''' (of type DateTime) – Defines the date and time when request was created.
* '''DE4AResponse''' (of type Any) – Contains the main DE4A data model.

The following example code shows a complete DE4A RegRep query response.<pre>
<query:QueryResponse xmlns:lcm="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:4.0" xmlns:query="urn:oasis:names:tc:ebxml-regrep:xsd:query:4.0" xmlns:spi="urn:oasis:names:tc:ebxml-regrep:xsd:spi:4.0" xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:4.0" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:4.0" status="urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Success" requestId="reqid">
<rim:Slot name="SpecificationIdentifier">
<rim:SlotValue xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="rim:StringValueType">
<rim:Value>de4a-iem-v2</rim:Value>
</rim:SlotValue>
</rim:Slot>
<rim:Slot name="IssueDateTime">
<rim:SlotValue xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="rim:DateTimeValueType">
<rim:Value>2023-01-28T20:18:46.598+01:00</rim:Value>
</rim:SlotValue>
</rim:Slot>
<rim:RegistryObjectList>
<rim:RegistryObject id="910a4e63-a08d-4d8b-b736-e94e9098b1fd">
<rim:Slot name="DE4AResponse">
<rim:SlotValue xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="rim:AnyValueType">

</rim:SlotValue>
</rim:Slot>
</rim:RegistryObject>
</rim:RegistryObjectList>
</query:QueryResponse>
</pre>

EDelivery

2023-03-01T08:53:33Z

Javier.ferrero:

The exchange of a single document between a DE and a DO always requires two eDelivery exchanges: the first one initiated by DE and targeted for DO, and the second one is initiated by DO and targeted for the DE. Technically speaking both transmissions are “requests” even though their semantics are “request” and “response”.

The foundation of the document exchange is the so called “4-corner model”, which differentiates between the business sender of a document (Corner 1 aka C1), the technical sender of a document (Corner 2 aka C2), the technical receiver of a document (Corner 3 aka C3) and the business receiver of a document (Corner 4 aka C4). Depending on the order of a message exchange, the assignment of the corner varies. In DE4A the “DE4A Connector” (sometimes just “Connector”) can play the role of both DR and DT and therefore acts as C2 or C3, depending on whether a message is sent or received.
[[File:EDelivery business request from DE to DO.png|none|frame|eDelivery business request from DE to DO]]
The figure above depicts the structural message exchange initiated by DE (C1), sent by DR (C2), received by DT (C3) and forwarded to DO (C4). The message exchange between C1 and C2 as well as the message exchange between C3 and C4 are not specified by eDelivery, even though AS4 may be used for this, but they must be defined by the DE4A Connector.

If DO sends a message back to DE, the order of the messages change as well as the corner assignment, as shown in the following figure where the DO becomes C1, forwarding the response to DT which is now C2. The AS4 transmission targets DR as C3 who in turn forwards the payload to DE which is the C4 in this scenario.
[[File:EDelivery business response from DO to DE.png|none|frame|eDelivery business response from DO to DE]]
This duality of the message exchange means, that each of the named nodes (DE, DR, DT and DO) requires both sending and receiving capabilities.

For the sake of clarity, the rest of the document only shows images with messages flowing from DE to DO because it seems easier to understand, even though the image would be perfectly valid for the return direction from DO to DE (except when stated differently).

The eDelivery message exchange in DE4A uses the so called “Dynamic Discovery” which is an extension of the basic eDelivery in the sense that it adds the usage of SML and SMP. Both components as well as the lookup process are described below.

== Identification of components ==
Each C1 and C4 of a message exchange is called a “Participant” and is uniquely identified by a “Participant Identifier”. The nodes C2 and C3 are not participants and have no respective identifier, they are only accessed by URLs.

Different types of documents exchanged via eDelivery are classified via “Document Type Identifiers”. The orchestrations in which document types are exchanged are classified via “Process Identifiers”.

There is a separate policy document on the usage of identifiers within its network. This document, called [[Media:DE4A Policy for use of identifiers.pdf|DE4A Policy for use of identifiers.pdf]], contains the details about the following identifier types:

* Participant Identification
* Type Identification
* Process Identification
* Transport Profile Identification

Each Participant ID, Document Type ID and Process ID consists of two separate parts – one “scheme” part and one “value” part. A scheme defines the layout and constraints of the value. This allows to add new types of identifiers in different scenarios, without interfering with existing used identifiers.

== SML/DNS ==

== SMP ==

== AS4 ==

2022-12-16T18:58:08Z

Javier.ferrero: Javier.ferrero uploaded a new version of File:DE4A network IT2 v2-Target infrastructure it2.drawio.png

DE4A common specifications and components it2

2022-12-16T18:56:28Z

Javier.ferrero: New information and chapters.

This section provides an overview of the common components and specifications required for the evidence exchanges. The image bellow depictes the target, general infrastructure of the DE4A network.
[[File:DE4A network IT2 v2-Target infrastructure it2.drawio.png|center|thumb|1142x1142px]]
The following table describes the '''common''' components in the above diagram, leaving out those components that are developed or deployed directly by each DE4A participant, namely the Data Evaluator, the Data Owner and the eIDAS Nodes.
{| class="wikitable"
|+
!Component
!Description
|-
|DE4A Connector
|Technical proxy that allows the final participants to send requests for evidence or responses to other final participants over an eDelivery communication environment
|-
|SML
|The Service Metadata Locator. Reference instance in the DE4A network
|-
|SMP
|Service Metadata Publisher
|-
|AS4 Gateway
|AS4 protocol implementation for the message exchange
|-
|Central IAL
|Central component that allows to retrieve the information of the IAL functionality and the content of the MOR component
|-
|SSI Authority Agent
|Enterprise-level solution that enables issuing and submitting diplomas in the form of verifiable credentials/presentations to Issuers/Verifiers.
|-
|SSI Edge Agent
|Mobile digital wallet solution that enables users to manage their digital diplomas and interact with the Issuer's/Verifier's portals.
|}

== Getting started guide ==
When starting with iteration 2 developments, every partner should follow the [[getting started guide]].

== Checklist for Connectathons ==
A quick guide of points to consider and review prior to the Connectathon sessions has been developed to make the Connectathon sessions more productive. It is available [[DE4A Checklist for Connectathon|here]].
== Common specifications ==
===Usage of third-party specifications and components===
It comprises a list of elements and a description of the third-party libraries and components that have made it possible to build the DE4A components more quickly and allow them to be extended, thus increasing the stability and robustness of the system.

==== eDelivery ====

==== RegRep ====

==== Kafka ====

==== Directory ====

===[[Common behaviour and interactions between components]]===
Introduction to the chapter, highlighting the fact that the description of the behaviour is done through communication diagrams. Links to the five communication diagrams and the data dictionary.

=== Central IAL interface ===

===[[Summary of software interfaces.|Summary of software interfaces]]===
REST APIs interfaces refer to most of the components involved in the exchange of messages.

===[[DE4A Logs and error messages it2|DE4A Logs and error messages]]===
Definition and reference of error coding and logs handling. It includes standardised log and error messages within the DE4A project to provide a good understanding of the different components regarding their points of failure and the different states in which each system is placed.

== Common Components ==

===[[DE4A Connector it2|DE4A Connector]]===
The main component of the DE4A communication infrastructure for processing request and response messages from DP/DCs. The DE4A connector handles the message exchange process and obtains information from different nodes like IDK or SMP for this purpose. It implements the AS4 Gateway functionality, so it can undertake either Requestor or Transferor roles.

==== [[Installation and configuration guide of the DE4A Connector it2]] ====
Step by step guide to successful configure an instance of the DE4A Connector. Find in this section all aspects related to the different configuration scenarios and keypoints of the system.

=== Central IAL ===

=== [[DE4A SSI Authority Agent]] ===

The enterprise-level component of the SSI infrastructure for issuing and validating diplomas in the form of Verifiable Credentials.

==== [[Installation and configuration guide of the DE4A SSI Authority Agent it2]] ====
Step-by-step guide for a successful configuration of an Authority Agent instance. Find in this section all aspects related to the different configuration scenarios and REST API endpoint information.

=== [[DE4A SSI Edge Agent]] ===

== Testing infrastructure ==

=== [[DE4A Playground it2|DE4A Playground]] ===
It comprises a set of components and utilities provided for pilots and partners for testing purposes. In addition it can be used to replace some components that might not yet be available or that they need to be tested in a "real" environment.

=== [[Sample datasets]] ===
This page contains the information for the test cases available in the playground environment.

== DE4A Member States Infrastructure ==
Status of the DE4A Member States infrastructure for the second iteration of the pilots, along with some useful information to bear in mind when setting up such infrastructure.

=== [[Useful information on pilots and participants]] ===
[[Category:Wip]]

DE4A Connector it2

2022-12-16T18:13:46Z

Javier.ferrero: /* AS4 implementations */

The DE4A Connector is a technical proxy that allows the final participants (DE or DO) to send requests for evidence or responses to other final participants over an [[Usage of third party specifications and components|eDelivery]] communication environment. In addition, to handle the message exchange process, the Connector is responsible for obtaining the message routing information, by exchanging information with external components such as the Central IAL, the [[Usage of third party specifications and components|SML/DNS]] or the [[SMP]].

To do so, it provides a common interface to DEs and DOs, making the complexity of the system transparent to the final participants and integration easier.

The Connector component provides the [[AS4 Gateway]] functionality, so it can assume both the role of Data Requestor and Data Transferor. This approach makes the Connector a stand-alone web application that can be deployed on any suitable application server.

The security and integrity of messages, as well as the unique identification of the participants involved, are the cornerstones of the Connector component.[[File:DE4A network IT2 v2-Target infrastructure it2.drawio.png|alt=|center|frame|Conceptual schema of the target DE4A system for the second iteration.]]

== Functionalities provided ==
The main purpose of the DE4A Connector is sending and receiving evidence requests and their responses. The message exchange process is described in the DE4A deliverables D2.4 Project Start Architecture and D5.3 Initial technical design of interfaces.

=== Routing information lookup ===
The DE4A Connector is responsible for obtaining the Data Provider information from the [[DE4A Issuing Authority Locator (IAL)|Central IAL]]. The Central IAL collects information from all the SMPs deployed at each partner infrastucture and offers it in a centralized way through the REST API <code>/lookupRoutingInformation</code>. When queried about a Canonical Item (Evidence or Event Catalogue) and a country, it returns the identifier of the Data Owner to request that Canonical Item from in that country. Therefore, through this functionality, the DE4A Connector implements the [[DE4A Issuing Authority Locator (IAL)|IAL]] semantic tool.

=== Dynamic discovery of services ===
In order for the Connector to be able to send a message to the corresponding endpoint, the [[Usage of third party specifications and components|eDelivery]] dynamic discovery mode of operation is used. This operation mode is based on the use of the components of the eDelivery infrastructure: [[Usage of third party specifications and components|SML/DNS]] and SMPs. Through this functionality, the DE4A Connector implements the [[DE4A Evidence Service Locator (ESL)|ESL]] semantic tool.

The main elements stored in the SML/DNS and SMPs for this purpose are the following:

* ''ParticipantIdentifier'': The Data Owner/Data Evaluator identifier who is publishing its [[Usage of third party specifications and components|AS4]] communication point (or the Connector linked to it).
* ''DocumentTypeIdentifier'': Canonical Evidence Type or Canonical Event Catalogue.
* ''ProcessIdentifier'': Orchestration type: request, response or notification.
* ''AS4'' endpoint: AS4 service endpoint URL.
* ''Certificate'': The X.509 certificate of the AS4 server, used to encrypt the transmitted data for this specific participant.

The information described above is managed by the SML/DNS and SMP components and is used by the Connector when working with the phase4 implementation of AS4.

Focusing on the SML/DNS/SMP data retrieval, the process will take place according to the following features:

* SSL/TLS communication is mandatory.
* Response signature validation is mandatory.
* The communication between SMP and SML requires the usage of a client certificate.
The service metadata lookup will be performed as a step prior to the [[Usage of third party specifications and components|AS4]] message exchange. Therefore, the participant IDs and other related information must be known by the DE4A Connector in advance.

=== Supported interaction patterns ===
Interaction patterns define the flow of data through the Connector and the intercommunication between the different components. Each pattern exchanges certain types of messages, and the incoming/outgoing information will depend on the processes occurring in the external components.

The Connector currently supports four interaction patterns: [[Intermediation Pattern|Intermediation (IM)]], [[User-supported Intermediation Pattern|User-Supported intermediation (USI)]], [[Subscription and Notification Pattern|Subscription and Notification (S&N)]] and [[Lookup Pattern|Lookup (LU)]] patterns. The [[Verifiable Credentials Pattern|Verifiable Credentials (VC)]] pattern is not supported by the DE4A Connector since that interaction pattern has benn implemented through its own components: the [[DE4A SSI Authority Agent|SSI Authority Agent]] and the [[DE4A SSI Edge Agent|SSI Edge Agent]].

Most of the specific behaviour of each interaction pattern is independent of the Connector itself, as the Connector component is just designed to exchange messages and the main differences between the patterns take place in the external components such as the Data Evaluator and the Data Owner.

Additionally, the DE4A Connector offers a '''backwards compatibility feature''' for the former synchronous IM pattern. It can handle the old messaging structure, so the synchronous implementation is fully compatible with the current asynchronous version.

=== Connector roles ===
A Connector instance can play two different roles:

* Data Requestor (DR)
* Data Transferor (DT)

No configuration is needed to differentiate the roles, it only depends on the usage, i.e., the behaviour will be according to the messages sent. Moreover, in a functional scenario, the SMP data will determine which Connector is playing the DR or DT role.

=== AS4 implementations supported ===
The message exchange is built on the [[Usage of third party specifications and components|AS4]] protocol, which is an open standard for secure, payload-agnostic, business-to-business document exchange via web services. Secure document exchange is governed by WS-Security aspects, including XML Encryption and XML Digital Signatures.

==== phase4 ====
The DE4A Connector implements phase4 as a gateway to perform the AS4 message exchange.
* '''Main features'''
** It is a generic AS4 solution.
** It can be integrated in basically any Servlet-based application server.
** It can easily be used with Peppol.
** It can be used with other Dynamic Discovery solutions.
** It supports a high degree of customization.
** It is not limited to the CEF/e-SENS profile.

All necessary configuration parameters are provided by the properties file of the DE4A Connector.

=== Error handling ===
Since the Connector performs multiple communications between different external components and some data and structure validations are performed, the Connector needs to monitor all failure points and be able to identify them in order to build the corresponding messages and warnings to inform each external component. When an error happens, the corresponding component creates an error message with the information about the error to be sent back to the entity that sent the failed message.

The error handling is based on the set of [[DE4A Logs and error messages it2|log and error messages]] defined for DE4A.

=== Kafka messages ===
Within the data flow and message exchange, there are many key points where it is important to know how the data is being managed, as well as identifying intermediate errors and unhandled system states. In this respect, the Connector can send messages to a [[Usage of third party specifications and components|Kafka]] server to track the data flow and trace the state of the system at certain points.

This feature is an advantage from a technical and business point of view, as the Connector performs the message exchange transparently to the other components.

It should be noted that the messages sent to the Kafka server are hardcoded, it is not a parameterizable feature, so any enhancements must be hardcoded again and deployed. It has been developed in such a way because the necessity of a Kafka server is not expected outside the DE4A project. In a real scenario, an alternative way of collecting logs should be implemented.

==== Message types ====
The Connector implements a [[Usage of third party specifications and components|Kafka]] message producer through the de4a-kafka-client library of the de4a-commons package. This producer provides several types of messages or severity levels:

* '''Success'''
* '''Info'''
* '''Warn'''
* '''Error'''
* '''Fatal error'''

Those message categories can be easily used to specify the severity level of the message sent to the Kafka server to track and identify them.

==== List of messages ====
The messages currently sent from the Connector to the Kafka server are as follows:

'''Services''' – ''(Info level)''

* RequestTransferEvidenceIM message received - RequestId: <code>{0}</code>, CanonicalEvidenceType: <code>{1}</code>, DataEvaluator: <code>{2}</code>, DataOwner: <code>{3}</code>
* RequestTransferEvidenceUSI message received - RequestId: <code>{0}</code>, CanonicalEvidenceType: <code>{1}</code>, DataEvaluator: <code>{2}</code>, DataOwner: <code>{3}</code>
* RequestTransferEvidenceUSIDT message received - RequestId: <code>{0}</code>
* RequestLookupRoutingInformation message received - CanonicalEvidenceType: <code>{0}</code>, CountryCode: <code>{1}</code>, DataOwnerId: <code>{2}</code>
* Sending request to IDK - URL: <code>{0}</code>
* Looking for Data Owner address - DataOwnerId: <code>{0}</code>

'''Client''' – ''(Info level)''

* Requesting to SMP - ParticipantId: <code>{0}</code>, DocumentTypeId: <code>{1}</code>, MessageType: <code>{2}</code>
* Sending RequestForwardEvidence to the Data Evaluator - RequestId: <code>{0}</code>, DataEvaluatorId: <code>{1}</code>, DataOwnerId: <code>{2}</code>, Endpoint: {3}
* Sending RequestExtractEvidence IM to the Data Owner - RequestId: <code>{0}</code>, CanonicalEvidenceType: <code>{1}</code>, DataEvaluatorId: <code>{2}</code>, DataOwnerId: <code>{3}</code>, Endpoint: <code>{4}</code>
* Sending RequestExtractEvidence USI to the Data Owner - RequestId: <code>{0}</code>, CanonicalEvidenceType: <code>{1}</code>, DataEvaluatorId: <code>{2}</code>, DataOwnerId: <code>{3}</code>, Endpoint: <code>{4}</code>

'''AS4''' – ''(Info level)''

* Sending request message via AS4 gateway - DataEvaluatorId: <code>{0}</code>, DataOwnerId: <code>{1}</code>, CanonicalEvidenceType: <code>{2}</code>
* Sending response message via AS4 gateway - DataEvaluatorId: <code>{0}</code>, Message tag: <code>{1}</code>, CanonicalEvidenceType: <code>{2}</code>
* Processing the request received via AS4 gateway - RequestId: <code>{0}</code>
* Processing the response received via AS4 gateway - RequestId: <code>{0}</code>

'''Errors''' – ''(Error level)''

* The corresponding request to the received response is not found on database - RequestId: <code>{0}</code>
* RequestForwardEvidence has not been sent, unknown Data Evaluator endpoint - RequestId: <code>{0}</code>, DataEvaluatorId: <code>{1}</code>
* RequestTransferEvidence not found on AS4 incoming message
* Error processing incoming message from AS4 gateway
* Error building URI from Data Evaluator endpoint: <code>{0}</code>
* Error sending message to Data Requestor via AS4 gateway - RequestId: <code>{0}</code>
* Data Owner address not found - DataOwnerId: <code>{0}</code>
[1] The <code>{x}</code> symbols are placeholders for dynamic text to be logged.

===Data management===
The Connector stores and manages certain information such as DE endpoints (not to be confused with SMP endpoints), DO endpoints, certain request records for asynchronous response matching, etc. All this data and where to find it is described in the following subsections.

====Data Owner and Data Evaluator addresses====
Once each Data Owner is publishing his Connector service information on the SMP, the request will arrive to that Connector service configured on the SMP (via the AS4 Gateway), and considering that one Connector could be serving to multiples DOs, this Connector has to know the addressing (base endpoint, without path name) information related to a specific participant identifier (e.g. iso6523-actorid-upis::9999:egov) to send forward the request to the corresponding Data Owner, so due to that, the Connector has a configuration file '''de-do.json''' where the information for the data owner and/or the Data Evaluator endpoints is stored. More information is available at [[Connector iteration 2 installation and configuration guide]].
==Security==
The message exchange performed by the Connector has been conceived to ensure different security aspects as:

*'''Authenticity''': ensures the identity of the participant entities and any common component involved in the message exchange. It is achieved through the participant identifiers definition, [[Usage of third party specifications and components|eDelivery]] specification and [[Usage of third party specifications and components|AS4]] implementations.

* '''Integrity''': refers to the accuracy and completeness of data. Security controls focused on integrity are used to prevent data from being modified or misused by an unauthorized party, provided by the WS-security and XML message signature.

*'''Confidentiality''': data confidentiality at message level could be achieved by taking advantage of WS-Security encryption feature in User messages. This message encryption is performed via asymmetric keys: the sender of the message encrypts with the public key of the recipient, so the message can only be decrypted by the recipient, who owns the private key. Those keys should be configured either in the Connector in case of phase4 or in any external AS4 gateway.

===Communications===
The Connector creates a secure context to establish in/outgoing connections with external components.

The main elements for such communication securitisations are:

*'''Private key''': private part of private-public key pair used in the TLS handshake between your server and the connecting clients. This private key must be configured in the Connector properties in order to create the secure context as well in the web server, in the case of reverse proxy or any similar structure. The keys configured on each component are generated under the DE4A management.

*'''Truststore''': used for the storage of certificates from the trusted Certificate Authority (CA), which is used in the verification of the certificate provided by the server in an SSL connection. The Connector provides a default truststore which allows to trust on certificates generated under the main DE4A CA.

====HTTP Proxy mode====
Sometimes, the environments have certain communication structure where the outgoing connections must be performed through an HTTP proxy server. The Connector provides de functionality and proper configuration to perform the communications via an HTTP proxy server.
===Message cryptographic protection ===
The Connector messages exchange can be separated into:

====REST APIs messages====
Once the SSL connection is established, all the data exchanged through it, will be encrypted on transport level based on the SSL context configuration settled, either managed by a reverse proxy on the server environment or configuring the proper application properties.

====AS4 messages====

*'''Phase4''': internally the message is encrypted using a specific keystore configuration only used for this purpose; also the cross-gateways communications are additionally encrypted over the HTTPS secure protocol.

===Message validation===
Message validation is performed at different stages of the Connector data flow, from message structure compliance to content integrity.

====Schema validation====
All the messages produced and consumed by the Connector are performing an XML Schema validation once it is received or sent out. This validation is done by the object conversion library that keeps the schema model including all the structure and content constraints.

====Signature validation====
As well as the XML Schema validation, the Connector performs validations to ensure the content and reliability on certain phases of the message exchange process:

*Services metadata querying
*In the SMP data exchange a message signature validation is being performed to maintain the content reliability. This validation consists of verifying the embedded signature on the message against the trust certificate configured in the Connector for that purpose.
The signature of incoming AS4 messages is verified against the central [[Usage of third party specifications and components|AS4]] Gateway CA globally used in DE4A project, internally validated by the implementation libraries that handle the reception and delivery.

==Technology used==

===System core architecture===
The Connector works as standalone application that runs different web services according to the RESTful API architecture principles. The application is built with the following tools:

*Spring Framework version 5.x.
*Java 11
*Apache HTTP Client 4.x

In addition to the core architecture, the XML Schemas defined to model the exchanged information, data constraints, interfaces, etc. are also important. All this is part of the Connector core through the de4a-commons library, which contains the above-mentioned model as well as utilities and conversion tools.

*Author: ''DE4A (WP5)''
*Repository: https://github.com/de4a-wp5/de4a-commons

===Third party libraries===
As part of the bunch of libraries used by the Connector there are some of the related with the core features and which represent a starting point for the functionalities provided by the Connector.

==== TOOP Connector====
The TOOP Connector is a set of shared utility functions used in the Connector to perform common tasks that are required for a safe and interoperable data exchange. In the initial iteration the latest version of the TOOP Connector technical components were reused mainly for the usage of the built-in phase4 AS4 Gateway. Other elements of the TOOP Connector are currently ignored.

*Author: ''TOOP Project''
*Repository: https://github.com/de4a-wp5/toop-connector-ng

====ph-oton libraries====
Set of Java libraries to build Java web applications.

*Author: ''Philip Helger (phax)''
*Repository: https://github.com/phax/ph-oton

====Peppol commons libraries====
They include the SMP client library used by the Access Points to retrieve service metadata. This library supports the Peppol SMP specification, the OASIS BDXR SMP v1 and OASIS BDXR SMP v2 specification. This project uses Apache HTTP client to perform the REST lookups on foreign SMPs.

*Author: ''Philip Helger (phax)''
*Repository: https://github.com/phax/peppol-commons

=== Data management===
To manage the model and the data stored by the Connector the following technologies are used:

*'''JPA:''' The Java Persistence API is a specification of Java. It is used to persist data between Java object and relational database. JPA acts as a bridge between object-oriented domain models and relational database systems. As JPA is just a specification, it does not perform any operation by itself.

*'''Hibernate:''' An object–relational mapping tool for the Java programming language. It provides a framework for mapping an object-oriented domain model to a relational database. Hibernate handles object–relational impedance mismatch problems by replacing direct, persistent database accesses with high-level object handling functions.

===Utilities libraries===
The project uses several libraries and utilities to process and transform the data. They can be divided according to their nature:

*'''Commercial libraries'''

To perform common and non-business operations on web and data exchange projects, the Connector uses different commercial solutions, also all the libraries embedded in the Java development kit.

*'''In-house solutions'''
The Connector project includes some utilities that allow the data processing and internal tools to perform all the Connector tasks. Those utilities are within the Connector project as a module called ''de4a-commons.''
[[Category:Wip]]

DE4A common specifications and components it2

2022-12-16T17:29:36Z

Javier.ferrero: /* DE4A SSI Edge Agent */

This section provides an overview of the common components and specifications required for the evidence exchanges.

== Getting started guide ==
When starting with iteration 2 developments, every partner should follow the [[getting started guide]].

== Checklist for Connectathons ==
A quick guide of points to consider and review prior to the Connectathon sessions has been developed to make the Connectathon sessions more productive. It is available [[DE4A Checklist for Connectathon|here]].
== Common specifications ==
===Usage of third-party specifications and components===
It comprises a list of elements and a description of the third-party libraries and components that have made it possible to build the DE4A components more quickly and allow them to be extended, thus increasing the stability and robustness of the system.

==== eDelivery ====

==== RegRep ====

==== Kafka ====

===[[Common behaviour and interactions between components]]===
Introduction to the chapter, highlighting the fact that the description of the behaviour is done through communication diagrams. Links to the five communication diagrams and the data dictionary.

===[[Summary of software interfaces.|Summary of software interfaces]]===
REST APIs interfaces refer to most of the components involved in the exchange of messages.

===[[DE4A Logs and error messages it2|DE4A Logs and error messages]]===
Definition and reference of error coding and logs handling. It includes standardised log and error messages within the DE4A project to provide a good understanding of the different components regarding their points of failure and the different states in which each system is placed.

== Common Components ==

===[[DE4A Connector it2|DE4A Connector]]===
The main component of the DE4A communication infrastructure for processing request and response messages from DP/DCs. The DE4A connector handles the message exchange process and obtains information from different nodes like IDK or SMP for this purpose. It implements the AS4 Gateway functionality, so it can undertake either Requestor or Transferor roles.

==== [[Installation and configuration guide of the DE4A Connector it2]] ====
Step by step guide to successful configure an instance of the DE4A Connector. Find in this section all aspects related to the different configuration scenarios and keypoints of the system.

=== Issuing Authority Locator ===

=== [[DE4A SSI Authority Agent]] ===

The enterprise-level component of the SSI infrastructure for issuing and validating diplomas in the form of Verifiable Credentials.

==== [[Installation and configuration guide of the DE4A SSI Authority Agent it2]] ====
Step-by-step guide for a successful configuration of an Authority Agent instance. Find in this section all aspects related to the different configuration scenarios and REST API endpoint information.

=== [[DE4A SSI Edge Agent]] ===

== Testing infrastructure ==

=== [[DE4A Playground it2|DE4A Playground]] ===
It comprises a set of components and utilities provided for pilots and partners for testing purposes. In addition it can be used to replace some components that might not yet be available or that they need to be tested in a "real" environment.

=== [[Sample datasets]] ===
This page contains the information for the test cases available in the playground environment.

== DE4A Member States Infrastructure ==
Status of the DE4A Member States infrastructure for the second iteration of the pilots, along with some useful information to bear in mind when setting up such infrastructure.

=== [[Useful information on pilots and participants]] ===
[[Category:Wip]]

Useful information on pilots and participants

2022-11-30T15:08:49Z

Javier.ferrero: /* SMP in Member States */

Useful information about the pilots and the participants in DE4A during the second iteration of the project. This information is intended to serve as a reference for the configuration and operation of the partners' infrastructures and the Playground. Each partner is responsible for entering and keeping the information collected on this Wiki page up-to-date.

== Progress of the deployment of DE4A participants' infrastructures in iteration 2 ==

=== SMP in Member States ===
{| class="wikitable"
!MS
!Member State
!Participant
!Own SMP (Deployed & configured / In progress / No, planned for X)
|-
|'''AT'''
|Austria
|BRZ
|Deployed and configured, phoss 5.7.1, Telesec Certificates
|-
|'''ES'''
| Spain
|SGAD
| Deployed and configured: phoss SMP v5.6.2, CommisSign2 Certificates
|-
|'''LU'''
|Luxembourg
|CTIE
|Not deployed, prevision "before light review"
|-
|'''NL'''
|The Netherlands
|RVO
|Deployed, solving configuration issues
|-
|'''PT'''
| Portugal
|AMA
|Deployed and configured
|-
|'''RO'''
| Romania
|ONRC
|Deployed and configured
|-
|'''RO'''
| Romania
|MoAI
|Not yet deployed
|-
|'''SU'''
|Sweden
|BVE
|Deployed and configured
|-
|'''SI'''
| Slovenia
|SI-MPA
|Deployed and configured to use IAL, configuration verified by Philip
|}

===DE4A Connector in Member States===
{| class="wikitable"
!MS
!Member State
!Participant
!Own Connector (Deployed & configured / In progress / No, planned for X)
|-
|'''AT'''
|Austria
|BRZ
|
|-
|'''ES'''
|Spain
|SGAD
|Deployed & configured: v0.3.1, CommisSign2 Certificates
|-
|'''LU'''
|Luxembourg
|CTIE
|
|-
|'''NL'''
|The Netherlands
|RVO
|Deployed & Configured: v02.6 (Test environment)
|-
|'''PT'''
|Portugal
|AMA
|
|-
|'''RO'''
| Romania
|ONRC
|
|-
|'''RO'''
|Romania
|MoAI
|
|-
|'''SU'''
|Sweden
|BVE
|
|-
|'''SI'''
|Slovenia
|SI-MPA
|Deployed & configured: v0.2.6
|}
== Summary of pilots and participants during the second iteration ==

=== Summary of DE4A pilots IT2 ===
{| class="wikitable"
! colspan="5" |Iteration 2
|-
|'''Pilot'''
|'''Use case'''
|'''Use case name'''
|'''Interaction pattern used'''
|'''Evidence exchanged'''
|-
| rowspan="3" |'''Studying abroad (SA)'''
|UC1.1
|Application to public higher education
|User-Supported Intermediation (USI)
|Higher Education Diploma
Secondary Education Diploma
|-
|UC1.2
|Applying for study grant
|User-Supported Intermediation (USI)
|Higher Education Diploma
Large Family Evidence

Disability Evidence
|-
|UC1.3
|Diploma / Certs / Studies / Professional recognition
|Verifiable Credentials (VC)
|Higher Education Diploma
|-
| rowspan="2" |'''Doing business abroad (DBA)'''
|UC2.1
|Starting a business in another Member State
|Intermediation (IM)
Subscription and Notification (S&N)
|Company Registration
|-
|UC2.2
|Doing business in another Member State
|Intermediation (IM)
Subscription and Notification (S&N)

Lookup (LU)
|Company Registration
"Business events" catalogue
|-
| rowspan="2" |'''Moving abroad (MA)'''
|UC3.1
|Request address change
|Registration: User-Supported Intermediation (USI)
Deregistration: Notification (S&N) and Lookup (LU)
|Domicile Registration Evidence
|-
|UC3.2
|Request an extract or copy of civil state certificate
|User-Supported Intermediation (USI)
|Birth Evidence
Marriage Evidence
|}

=== DE4A pilot participants IT2 ===
{| class="wikitable"
! colspan="4" |Partner
! colspan="3" |SA
! colspan="2" |DBA
! colspan="2" |MA
!
|-
|'''Short name'''
|'''Name'''
|'''Country'''
|'''Participant ID'''
|'''UC1.1'''
|'''UC1.2'''
|'''UC1.3'''
|'''UC2.1'''
|'''UC2.2'''
|'''UC3.1'''
|'''UC3.2'''
|'''Notes'''
|-
|BMDW
|Bundesministerium fuer Digitalisierung und Wirtschaftsstandort
|AT
|iso6523-actorid-upis::9991:at000000271
|
|
|
|DE
DO
|DE

DO
|
|
|
|-
|BRZ
|Bundesrechenzentrum GMBH (Federal Data Center)
|AT
|
|
|
|
|DR
DT
|DR

DT
|
|
|BRZ has no Participant ID, because it is only DR and DT
|-
|SGAD
|Secretaría General de Administración Digital (General Secretariat for Digital Administration)
|ES
|iso6523-actorid-upis::9920:ess2833002e
|DR
DO,DT
|DO,DT
|DP
|
|
|DO,DT
|DE,DR
DO,DT
|Evidence in SA UCs is provided by the DE4A partner UJI.
|-
|UJI
|Universitat Jaume I de Castellón (Jaume I University of Castellón)
|ES
|iso6523-actorid-upis::9920:esq6250003h
|DE*
|
|
|
|
|
|
|*Connector provided by SGAD. UJI is also an evidence provider in all SA UCs through SGAD.
|-
|CTIE
|Centre des Technologies de l'Information de l'Etat (State Information Technology Center)
|LU
|iso6523-actorid-upis::9991:lu000000025
|
|
|
|
|
|DE,DR
DO,DT
|DE,DR
DO,DT
|
|-
|RVO
|Rijksdienst voor Ondernemend Nederland (Netherlands Enterprise Agency)
|NL
|iso6523-actorid-upis::9991:nl000000024-it1
|
|
|
|DE,DR
|DE,DR
|
|
|*9999:nl000000024-test-it1 for test environment
|-
|RVO
|Rijksdienst voor Ondernemend Nederland (Netherlands Enterprise Agency)
|NL
|iso6523-actorid-upis::9991:nl000000106-it1
|
|
|
|DO,DT
|DO,DT
|
|
|*9999:nnl000000106-test-it1 for test environment
|-
|AMA-IP
|Agencia para a Modernizacao Administrativa IP (Administration Modernization Agency)
|PT
|iso6523-actorid-upis::9991:pt000000026
|DR
DO,DT
|DT
|
|
|
|DR
DO,DT
|DR
|AMA-IP consults INESC-ID in some cases when the latter takes the role of DO. Therefore, INESC-ID does not directly take part of the DE4A network as DO, but AMA-IP instead.
|-
|INESC-ID
|Institute for Systems and Computer Engineering, Technology and Science
|PT
|iso6523-actorid-upis::9991:pt990000101
|DE
|
|DC
DP
|
|
|
|
|
|-
|MoAI
|Ministerul Afacerilor Interne (Ministry of Internal Affairs)
|RO
|iso6523-actorid-upis::9991:ro000000005
|
|
|
|
|
|DE,DR

DO,DT
|DE,DR

DO,DT
|
|-
|ORNC
|Oficiul National B22 al Registrului Comertului
|RO
|iso6523-actorid-upis::9991:ro000000006
|
|
|
|DE,DR

DO,DT
|DE,DR

DO,DT
|
|
|
|-
|BVE
|Bolagsverket (Companies Registration Office)
|SE
|iso6523-actorid-upis::9991:se000000013
|
|
|
|DE,DR
|DE,DR
|
|
|
|-
|JSI
|Institut "Jožef Stefan" (Jožef Stefan Institute)
|SI
|iso6523-actorid-upis::9949:si55560822
|
|DE
|
|
|
|
|
|
|-
|MIZŠ
|Ministrstvo za izobraževanje, znanost in šport (Ministry of Education, Science and Sport)
|SI
|iso6523-actorid-upis::9949:si14246821
|DE
DO
|
|DC
DP
|
|
|
|
|*The central preview functionality for DO is provided by SI-MPA.
|-
|SI-MPA
|Ministrstvo za javno upravo (Ministry of Public Administration)
|SI
|iso6523-actorid-upis::9991:si000000015
|DR
DT
|DR
|
|
|
|DR
DT
|DR
DT
|
|-
|MNZ
|Ministrstvo za notranje zadeve (Ministry of the Interior)
|SI
|iso6523-actorid-upis::9949:si52817652
|
|
|
|
|
|DO
|DO
|*The central preview functionality for DO is provided by SI-MPA.
|}

=== Technical information on participants IT2 ===
{| class="wikitable"
!
==== Test domain (Playground) ====
!
==== Pilot domain ====
|-
|
{| class="wikitable"
! colspan="4" |SMP
|-
|'''Country'''
|'''Participant'''
|'''SMP endpoint'''
|'''SMP certificate'''
|-
|ES (shared)
|SGAD
|[https://de4a.redsara.es/sgad-smp https://de4a.redsara.es/sgad-smp/]
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD owncloud folder]
|-
|NL
|RVO
|https://acc-eidas.minez.nl/de4a-smp/
|
|}
|
{| class="wikitable"
! colspan="4" |SMP
|-
|'''Country'''
|'''Participant'''
|'''SMP endpoint'''
|'''SMP certificate'''
|-
|AT
|BRZ
|https://de4a-smp.usp.gv.at/
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD&fileid=1169370 owncloud folder]
|-
|ES
|SGAD
|
|
|-
|LU
|
|
|
|-
|NL
|RVO
|https://acc-eidas.minez.nl/de4a-smp/
|
|-
|PT
|AMA
|[https://pprsmp.iap.gov.pt/ https://pprsmp.iap.gov.pt/smp.iap.gov.pt]
|
|-
|RO
|MOAI
|https://de4a-smp.mai.gov.ro:8443/
|
|-
|SE
|
|
|
|-
|SI
|SI-MPA
|https://toop-smp.pprod.medius.si/public
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SI-MPA owncloud folder]
|}
|-
|
{| class="wikitable"
! colspan="3" |DE
|-
|'''Participant'''
|'''Evidence types consumed'''
|'''DE e-procedure portal'''
|-
|BMDW
|Company Registration
|
|-
|SGAD
|Birth Evidence
Marriage Evidence
|https://pre-as4gw-dt-de4a.redsara.es/de4a-evaluator/
|-
|UJI
|Higher Education Diploma
|
|-
|CTIE
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|RVO
|Company Registration
|
|-
|INESC-ID
|Higher Education Diploma
Secondary Education Diploma
|
|-
|
|
|
|-
|MoAI
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|ORNC
|Company Registration
|
|-
|BVE
|Company Registration
|
|-
|JSI
|Higher Education Diploma
Large Family Evidence

Disability Evidence
|https://grants.e5.ijs.si/grants/public/
|-
|MIZŠ
|Higher Education Diploma
Secondary Education Diploma
|http://srvas2.rrc.si/prijava/?lang=en
|}
|
{| class="wikitable"
! colspan="3" |DE
|-
|'''Participant'''
|'''Evidence types consumed'''
|'''DE e-procedure portal'''
|-
|BMDW
|Company Registration
|
|-
|SGAD
|Birth Evidence
Marriage Evidence
|
|-
|UJI
|Higher Education Diploma
|
|-
|CTIE
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|RVO
|Company Registration
|https://mijn.rvo.nl/digital-europe-for-all-pilot

(production)
|-
|INESC-ID
|Higher Education Diploma
Secondary Education Diploma
|
|-
|
|
|
|-
|MoAI
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|ORNC
|Company Registration
|
|-
|BVE
|Company Registration
|
|-
|JSI
|Higher Education Diploma
Large Family Evidence

Disability Evidence
|
|-
|MIZŠ
|Higher Education Diploma
Secondary Education Diploma
|
|}
|-
|
{| class="wikitable"
! colspan="3" |DO
|-
|'''Participant'''
|'''Evidence types provided'''
|'''DO evidence portal'''
|-
|BMDW
|Company Registration
|
|-
|SGAD
|Higher Education Diploma
Secondary Education Diploma

Large Family Evidence

Disability Evidence

Domicile Registration Evidence

Birth Evidence

Marriage Evidence

Pension Evidence

Unemployment Evidence

Working Life Evidence
|Direct public access is not enabled
|-
|CTIE
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|RVO
|Company Registration
|
|-
|AMA-IP
|Domicile Registration Evidence
|
|-
|INESC-ID
|Higher Education Diploma
|
|-
|MoAI
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|ORNC
|Company Registration
|
|-
|MIZŠ
|Higher Education Diploma
|Direct public access is not enabled
|-
|MNZ
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|Direct public access is not enabled
|}
|
{| class="wikitable"
! colspan="3" |DO
|-
|'''Participant'''
|'''Evidence types provided'''
|'''DO evidence portal'''
|-
|BMDW
|Company Registration
|
|-
|SGAD
|Higher Education Diploma
Secondary Education Diploma

Large Family Evidence

Disability Evidence

Domicile Registration Evidence

Birth Evidence

Marriage Evidence

Pension Evidence

Unemployment Evidence

Working Life Evidence
|
|-
|CTIE
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|RVO
|Company Registration
|
|-
|AMA-IP
|Domicile Registration Evidence
|
|-
|INESC-ID
|Higher Education Diploma
|
|-
|MoAI
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|ORNC
|Company Registration
|
|-
|MIZŠ
|Higher Education Diploma
|Direct public access is not enabled
|-
|MNZ
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|Direct public access is not enabled
|}
|-
|
{| class="wikitable"
! colspan="3" |DR
|-
|'''Participant'''
|'''AS4 certificate'''
|'''Connector endpoint'''
|-
|BRZ
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD&fileid=1169370 owncloud folder]
|https://de4a.usp.gv.at/ado/phase4
|-
|SGAD
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD owncloud folder]
|https://pre-as4gw-dt-de4a.redsara.es/de4a-it2-connector/
|-
|CTIE
|
|
|-
|RVO
|
|[https://acc-eidas.minez.nl/de4a-connector/requestTransferEvidenceIM https://acc-eidas.minez.nl/de4a-connector/]

(iteration 2 version, but DE and DO are still it1 voor IM)
|-
|AMA-IP
|
|http://130.61.108.235/de4a-connector-it2/
|-
|ORNC
|
|
|-
|BVE
|
|
|-
|SI-MPA
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SI-MPA owncloud folder]
|https://toop-as4.pprod.medius.si/
|-
|RO-MOAI
|https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/RO-MOAI&fileid=1173820
|https://de4a.mai.gov.ro:8443/
|}
|
{| class="wikitable"
! colspan="3" |DR
|-
|'''Participant'''
|'''AS4 certificate'''
|'''Connector endpoint'''
|-
|SGAD
|
|
|-
|CTIE
|
|
|-
|RVO
|
|[https://eidas.minez.nl/de4a-connector/requestTransferEvidenceIM https://eidas.minez.nl/de4a-connector/]

(Still Iteration 1 version)
|-
|AMA-IP
|
|http://130.61.108.235/de4a-connector-it2/
|-
|ORNC
|
|
|-
|BVE
|
|
|-
|SI-MPA
|
|
|}
|-
|
{| class="wikitable"
! colspan="3" |DT
|-
|'''Participant'''
|'''AS4 certificate'''
|'''Connector endpoint'''
|-
|BRZ
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD&fileid=1169370 owncloud folder]
|https://de4a.usp.gv.at/ado/phase4
|-
|SGAD
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD owncloud folder]
|https://pre-as4gw-dt-de4a.redsara.es/de4a-it2-connector/
|-
|CTIE
|
|
|-
|RVO
|
|[https://acc-eidas.minez.nl/de4a-connector/requestTransferEvidenceIM https://acc-eidas.minez.nl/de4a-connector/]
|-
|AMA-IP
|
|http://130.61.108.235/de4a-connector-it2/
|-
|MoAI
|
|
|-
|ORNC
|
|
|-
|SI-MPA
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SI-MPA owncloud folder]
|https://toop-as4.pprod.medius.si/
|}
|
{| class="wikitable"
! colspan="3" |DT
|-
|'''Participant'''
|'''AS4 certificate'''
|'''Connector endpoint'''
|-
|BRZ
|
|
|-
|SGAD
|
|
|-
|CTIE
|
|
|-
|RVO
|
|[https://eidas.minez.nl/de4a-connector/requestTransferEvidenceIM https://eidas.minez.nl/de4a-connector/]

(Still Iteration 1 version)
|-
|AMA-IP
|
|http://130.61.108.235/de4a-connector-it2/
|-
|MoAI
|
|
|-
|ORNC
|
|
|-
|SI-MPA
|
|
|}
|}

===DE-DO.json participant endpoint urls===
{| class="wikitable"
!
====Test domain (PRE2b) ====
!
====Pilot domain (PRO2)====
|-
|
{| class="wikitable"
! colspan="5" |Data Owners
|-
|'''Country'''
|'''Participant'''
|'''Participant ID'''
|'''Pattern'''
|'''DO Endpoint URL'''
|-
| rowspan="4" |AT
| rowspan="4" |
| rowspan="4" |iso6523-actorid-upis::99XX:at000000271-test-it2
|IM
|
|-
|USI
|
|-
| LU
|
|-
|SN
|
|-
| rowspan="4" | ES
| rowspan="4" |SGAD
| rowspan="4" |iso6523-actorid-upis::9920:ess2833002e-test-it2
|IM
|https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/requestExtractEvidenceIM
|-
|USI
|https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/do1/usi/extractevidence
|-
|LU
|https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/dataOwner/in/lu/
|-
|SN
|https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/dataOwner/in/sn/
|-
| rowspan="4" |PT
| rowspan="4" |AMA
| rowspan="4" | iso6523-actorid-upis::99XX:pt000000026-test-it2
|IM
|
|-
|USI
|
|-
| LU
|
|-
|SN
|
|-
| rowspan="4" |NL
| rowspan="4" |RVO
| rowspan="4" |iso6523-actorid-upis::9999:nl000000106-test-it1
|IM
|
|-
|USI
|
|-
|LU
|
|-
|SN
|
|-
| rowspan="4" |SI
| rowspan="4" |MIZŠ
| rowspan="4" |iso6523-actorid-upis::9949:si14246821
|IM
|N/A
|-
|USI
|Not publicly disclosed
|-
|LU
|N/A
|-
|SN
|N/A
|-
|SI
|MNZ
|iso6523-actorid-upis::9949:si52817652
|USI
|Not publicly disclosed
|-
| rowspan="4" |SE
| rowspan="4" |BVE
| rowspan="4" |iso6523-actorid-upis::99XX:se000000013-test-it2
|IM
|
|-
|USI
|
|-
|LU
|
|-
|SN
|
|}
{| class="wikitable"
! colspan="5" |Data Evaluators
|-
|'''Country'''
|'''Participant'''
|'''Participant ID'''
|'''Response Type'''
|'''DE Endpoint URL'''
|-
| rowspan="4" | AT
| rowspan="4" |
| rowspan="4" |iso6523-actorid-upis::99XX:at000000271-test-it2
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" |ES
| rowspan="4" |SGAD
| rowspan="4" |iso6523-actorid-upis::9920:ess2833002e-test-it2
|response
|https://pre-as4gw-dt-de4a.redsara.es/de4a-evaluator/response/requestForwardEvidence
|-
|subscription_resp
|N/A
|-
|redirect
|https://pre-as4gw-dt-de4a.redsara.es/de4a-evaluator/response/usiRedirectUser
|-
|notification
|N/A
|-
| rowspan="4" | ES
| rowspan="4" |UJI
| rowspan="4" |iso6523-actorid-upis::9920:esq6250003h-test-it2
|response
|
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |PT
| rowspan="4" | INESC-ID
| rowspan="4" |iso6523-actorid-upis::9991:pt990000101-test-it2
|response
|
|-
|subscription_resp
| N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |NL
| rowspan="4" |RVO
| rowspan="4" |iso6523-actorid-upis::99XX:nl000000024-test-it1
|response
|N/A
|-
|subscription_resp
| N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |MIZŠ
| rowspan="4" |iso6523-actorid-upis::9949:si14246821
|response
|http://srvas2.rrc.si/de4a/requestForwardEvidence
|-
|subscription_resp
|N/A
|-
|redirect
|http://srvas2.rrc.si/de4a/redirectUser
|-
|notification
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |JSI
| rowspan="4" |iso6523-actorid-upis::9949:si55560822-test-it2
| response
| https://grants.e5.ijs.si/grants/public/de-r/requestForwardEvidence
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |SE
| rowspan="4" |BVE
| rowspan="4" |iso6523-actorid-upis::99XX:se000000013-test-it2
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|}
|
{| class="wikitable"
! colspan="5" |Data Owners
|-
|'''Country'''
|'''Participant'''
|'''Participant ID'''
|'''Pattern'''
|'''DO Endpoint URL'''
|-
| rowspan="4" |AT
| rowspan="4" |
| rowspan="4" |
|IM
|N/A
|-
|USI
|N/A
|-
| LU
|N/A
|-
|SN
|N/A
|-
| rowspan="4" | ES
| rowspan="4" |SGAD
| rowspan="4" |
|IM
|N/A
|-
|USI
|N/A
|-
|LU
|N/A
|-
|SN
|N/A
|-
| rowspan="4" |PT
| rowspan="4" |AMA
| rowspan="4" |
|IM
| N/A
|-
|USI
|N/A
|-
| LU
| N/A
|-
|SN
|N/A
|-
| rowspan="4" |NL
| rowspan="4" |RVO
| rowspan="4" |so6523-actorid-upis::9991:nl000000106-it1
|IM
|N/A
|-
|USI
|N/A
|-
|LU
|N/A
|-
|SN
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |MIZŠ
| rowspan="4" |iso6523-actorid-upis::9949:si14246821
|IM
|N/A
|-
|USI
|Not publicly disclosed
|-
|LU
|N/A
|-
|SN
|N/A
|-
|SI
|MNZ
|iso6523-actorid-upis::9949:si52817652
|USI
|Not publicly disclosed
|-
| rowspan="4" |SE
| rowspan="4" |BVE
| rowspan="4" |
|IM
|N/A
|-
|USI
|N/A
|-
|LU
|N/A
|-
|SN
|N/A
|}
{| class="wikitable"
! colspan="5" |Data Evaluators
|-
|'''Country'''
|'''Participant'''
|'''Participant ID'''
|'''Response Type'''
|'''DE Endpoint URL'''
|-
| rowspan="4" | AT
| rowspan="4" |
| rowspan="4" |
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" |ES
| rowspan="4" |SGAD
| rowspan="4" |
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" | ES
| rowspan="4" |UJI
| rowspan="4" |
|response
|
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |PT
| rowspan="4" | INESC-ID
| rowspan="4" |
|response
|
|-
|subscription_resp
| N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |NL
| rowspan="4" |RVO
| rowspan="4" |iso6523-actorid-upis::9991:nl000000024-it1
|response
|N/A
|-
|subscription_resp
| N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |MIZŠ
| rowspan="4" |iso6523-actorid-upis::9949:si14246821
|response
|
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |JSI
| rowspan="4" |iso6523-actorid-upis::9949:si55560822
| response
|
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |SE
| rowspan="4" |BVE
| rowspan="4" |
|response
| N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|}

|}

==DE4A infrastructure IT2==
===Playground infrastructure IT2===
The following diagram depicts the Playground infrastructure for the second iteration, with the deployment of its corresponding components.[[File:DE4A network IT2-Playground IT2.drawio.png|frame|alt=|none]]

===Pilot partners infrastructure flavours IT2 ===
The following two diagrams outline the general infrastructure expected from the Member States and partners involved in the pilots. Each Connector is in turn connected and exchanges data with the corresponding Connector (DR or DT) of the Playground or other partners.

At this stage, all DE4A participants are expected to follow the set-up A, while only Romania is expected to follow set-up B.[[File:DE4A network IT2-Country set-up A.drawio.png|frame|alt=|left]]

[[File:DE4A network IT2-Country set-up B.drawio.png|frame|alt=|none]]

== Domains and types of participant IDs ==

===DE4A domains===
In DE4A, there are two types of participants:

*Imaginary participants: intended to query the examples stored in the Mocked DO.
*Real participants: intended to retrieve data directly returned by partners.

At the same time, for the real participants, there are also two “domains”:

*Test domain: only fake data is used for test purposes. It is the domain related to the DE4A Playground, where participants return datasets from test sources.
*Pilot domain: real data from real citizens and companies is supposed to be used. It is the environment used for the running phase of the pilots, where participants access to their real registries and return real evidence from them.

Finally, the project is divided into two iterations where each of them needs a copy of those two domains, and where some overlap between them occurs.
[[File:Domain overlap.png|none|thumb|910x910px]]
As the DE4A project uses the dynamic discovery of eDelivery, where there cannot be duplicate participant IDs targeting to different Connectors (depending on the domain concerned), we need to define a different participant ID schema per each domain:

*'''PRE1a''': Imaginary participants stored in the Mocked DO for iteration 1 for testing. The related evidence is stored in the Mocked DO deployed in SGAD (ES).
** Scheme identifier used: “'''9999'''”.
** Suffix used: “'''-it1'''”.
**E.g. iso6523-actorid-upis::99'''99''':ess2833002e'''-it1'''

*'''PRE1b:''' Simulated data returned by the real participants used for testing in Playground iteration 1. The related evidence is located in each partner’s infrastructure, within their test domain.
**Scheme identifier used: “'''99XX'''”, where “XX” depends on the identifier each participant is using.
**Suffix used: “'''-it1'''”.
**E.g. iso6523-actorid-upis::99'''20''':ess2833002e'''-it1'''
*'''PRO1:''' Real data returned by the real participants during the execution of phase 1 of the pilot. The related evidence is located in each partner’s infrastructure, within their pilot domain.
**Scheme identifier used: “'''99XX'''”, where “XX” depends on the identifier each participant is using. It is the “real” participant ID.
**Suffix used: ''none'', since there is no overlap between phases 1 and 2 of the pilots.
**E.g. iso6523-actorid-upis::99'''20''':ess2833002e
*'''PRE2a:''' Imaginary participants stored in the Mocked DO for iteration 2 for testing. The related evidence is stored in the Mocked DO deployed in SGAD (ES).
**Scheme identifier used: “'''9999'''”.
**Suffix used: “'''-mock-it2'''”.
**E.g. iso6523-actorid-upis::99'''99''':ess2833002e'''-mock-it2'''
*'''PRE2b:''' Simulated data returned by the real participants used for testing in Playground iteration 2. The related evidence is located in each partner’s infrastructure, within their test domain.
**Scheme identifier used: “'''99XX'''”, where “XX” depends on the identifier each participant is using.
**Suffix used: “'''-test-it2'''”.
**E.g. iso6523-actorid-upis::99'''20''':ess2833002e'''-test-it2'''
*'''PRO2:''' Real data returned by the real participants during the execution of phase 2 of the pilot. The related evidence is located in each partner’s infrastructure, within their pilot domain.
**Scheme identifier used: “'''99XX'''”, where “XX” depends on the identifier each participant is using. It is the “real” participant ID.
**Suffix used: ''none'', since there is no overlap between phases 1 and 2 of the pilots.
**E.g. iso6523-actorid-upis::99'''20''':ess2833002e

Therefore, DE4A domains are differentiated by the participant ID schema used.

===Location of the participant IDs===
These different participant IDs must be stored in their corresponding IDKs and SMPs and configured to return the proper information:

*'''PRE1a:''' Imaginary participants
**IDK: none (for these participants, the mocked DE knows which the imaginary participants are and which DO to query, namely, the mocked DO of the first iteration).
**SMP: shared SMP of the Playground IT1. It returns the routing information of the targeted Connector (DR/DT) of the Playground IT1.
*'''PRE1b''': Simulated data from real participants
**IDK: mocked IDK of the Playground IT1.
**SMP: shared SMP of the Playground IT1. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.
*'''PRO1:''' Real data from real participants
**IDK: mocked IDK of the pilot running environment.
**SMP: national SMP of the requested participant. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.
***For the first pilot running phase, partners who have not yet deployed their own SMPs will be able to use a shared SMP provided by one of the partners with an available SMP. In such cases, the routing information of those partners will be stored in this shared SMP.
*'''PRE2a:''' Imaginary participants
**IDK: Central IAL. Its information is automatically updated and fed from the SMPs connected to it.
**SMP: shared SMP of the Playground IT2. It returns the routing information of the targeted Connector (DR/DT) of the Playground IT2.
*'''PRE2b:''' Simulated data from real participants
**IDK: Central IAL. Its information is automatically updated and fed from the SMPs connected to it.
**SMP: national SMP of the requested participant. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.
*'''PRO2:''' Real data from real participants
**IDK: Central IAL. Its information is automatically updated and fed from the SMPs connected to it.
**SMP: national SMP of the requested participant. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.

Useful information on pilots and participants

2022-11-30T12:34:11Z

Javier.ferrero: /* SMP in Member States */

Useful information about the pilots and the participants in DE4A during the second iteration of the project. This information is intended to serve as a reference for the configuration and operation of the partners' infrastructures and the Playground. Each partner is responsible for entering and keeping the information collected on this Wiki page up-to-date.

== Progress of the deployment of DE4A participants' infrastructures in iteration 2 ==

=== SMP in Member States ===
{| class="wikitable"
!MS
!Member State
!Participant
!Own SMP (Deployed & configured / In progress / No, planned for X)
|-
|'''AT'''
|Austria
|BRZ
|Deployed and configured, phoss 5.7.1, Telesec Certificates
|-
|'''ES'''
| Spain
|SGAD
| Deployed and configured: phoss SMP v5.6.2, Telesec Certificates
|-
|'''LU'''
|Luxembourg
|CTIE
|Not deployed, prevision "before light review"
|-
|'''NL'''
|The Netherlands
|RVO
|Deployed, solving configuration issues
|-
|'''PT'''
| Portugal
|AMA
|Deployed and configured
|-
|'''RO'''
| Romania
|ONRC
|Deployed and configured
|-
|'''RO'''
| Romania
|MoAI
|Not yet deployed
|-
|'''SU'''
|Sweden
|BVE
|Deployed and configured
|-
|'''SI'''
| Slovenia
|SI-MPA
|Deployed and configured to use IAL, configuration verified by Philip
|}

===DE4A Connector in Member States===
{| class="wikitable"
!MS
!Member State
!Participant
!Own Connector (Deployed & configured / In progress / No, planned for X)
|-
|'''AT'''
|Austria
|BRZ
|
|-
|'''ES'''
|Spain
|SGAD
|Deployed & configured: v0.3.1
|-
|'''LU'''
|Luxembourg
|CTIE
|
|-
|'''NL'''
|The Netherlands
|RVO
|Deployed & Configured: v02.6 (Test environment)
|-
|'''PT'''
|Portugal
|AMA
|
|-
|'''RO'''
| Romania
|ONRC
|
|-
|'''RO'''
|Romania
|MoAI
|
|-
|'''SU'''
|Sweden
|BVE
|
|-
|'''SI'''
|Slovenia
|SI-MPA
|Deployed & configured: v0.2.6
|}
== Summary of pilots and participants during the second iteration ==

=== Summary of DE4A pilots IT2 ===
{| class="wikitable"
! colspan="5" |Iteration 2
|-
|'''Pilot'''
|'''Use case'''
|'''Use case name'''
|'''Interaction pattern used'''
|'''Evidence exchanged'''
|-
| rowspan="3" |'''Studying abroad (SA)'''
|UC1.1
|Application to public higher education
|User-Supported Intermediation (USI)
|Higher Education Diploma
Secondary Education Diploma
|-
|UC1.2
|Applying for study grant
|User-Supported Intermediation (USI)
|Higher Education Diploma
Large Family Evidence

Disability Evidence
|-
|UC1.3
|Diploma / Certs / Studies / Professional recognition
|Verifiable Credentials (VC)
|Higher Education Diploma
|-
| rowspan="2" |'''Doing business abroad (DBA)'''
|UC2.1
|Starting a business in another Member State
|Intermediation (IM)
Subscription and Notification (S&N)
|Company Registration
|-
|UC2.2
|Doing business in another Member State
|Intermediation (IM)
Subscription and Notification (S&N)

Lookup (LU)
|Company Registration
"Business events" catalogue
|-
| rowspan="2" |'''Moving abroad (MA)'''
|UC3.1
|Request address change
|Registration: User-Supported Intermediation (USI)
Deregistration: Notification (S&N) and Lookup (LU)
|Domicile Registration Evidence
|-
|UC3.2
|Request an extract or copy of civil state certificate
|User-Supported Intermediation (USI)
|Birth Evidence
Marriage Evidence
|}

=== DE4A pilot participants IT2 ===
{| class="wikitable"
! colspan="4" |Partner
! colspan="3" |SA
! colspan="2" |DBA
! colspan="2" |MA
!
|-
|'''Short name'''
|'''Name'''
|'''Country'''
|'''Participant ID'''
|'''UC1.1'''
|'''UC1.2'''
|'''UC1.3'''
|'''UC2.1'''
|'''UC2.2'''
|'''UC3.1'''
|'''UC3.2'''
|'''Notes'''
|-
|BMDW
|Bundesministerium fuer Digitalisierung und Wirtschaftsstandort
|AT
|iso6523-actorid-upis::9991:at000000271
|
|
|
|DE
DO
|DE

DO
|
|
|
|-
|BRZ
|Bundesrechenzentrum GMBH (Federal Data Center)
|AT
|
|
|
|
|DR
DT
|DR

DT
|
|
|BRZ has no Participant ID, because it is only DR and DT
|-
|SGAD
|Secretaría General de Administración Digital (General Secretariat for Digital Administration)
|ES
|iso6523-actorid-upis::9920:ess2833002e
|DR
DO,DT
|DO,DT
|DP
|
|
|DO,DT
|DE,DR
DO,DT
|Evidence in SA UCs is provided by the DE4A partner UJI.
|-
|UJI
|Universitat Jaume I de Castellón (Jaume I University of Castellón)
|ES
|iso6523-actorid-upis::9920:esq6250003h
|DE*
|
|
|
|
|
|
|*Connector provided by SGAD. UJI is also an evidence provider in all SA UCs through SGAD.
|-
|CTIE
|Centre des Technologies de l'Information de l'Etat (State Information Technology Center)
|LU
|iso6523-actorid-upis::9991:lu000000025
|
|
|
|
|
|DE,DR
DO,DT
|DE,DR
DO,DT
|
|-
|RVO
|Rijksdienst voor Ondernemend Nederland (Netherlands Enterprise Agency)
|NL
|iso6523-actorid-upis::9991:nl000000024-it1
|
|
|
|DE,DR
|DE,DR
|
|
|*9999:nl000000024-test-it1 for test environment
|-
|RVO
|Rijksdienst voor Ondernemend Nederland (Netherlands Enterprise Agency)
|NL
|iso6523-actorid-upis::9991:nl000000106-it1
|
|
|
|DO,DT
|DO,DT
|
|
|*9999:nnl000000106-test-it1 for test environment
|-
|AMA-IP
|Agencia para a Modernizacao Administrativa IP (Administration Modernization Agency)
|PT
|iso6523-actorid-upis::9991:pt000000026
|DR
DO,DT
|DT
|
|
|
|DR
DO,DT
|DR
|AMA-IP consults INESC-ID in some cases when the latter takes the role of DO. Therefore, INESC-ID does not directly take part of the DE4A network as DO, but AMA-IP instead.
|-
|INESC-ID
|Institute for Systems and Computer Engineering, Technology and Science
|PT
|iso6523-actorid-upis::9991:pt990000101
|DE
|
|DC
DP
|
|
|
|
|
|-
|MoAI
|Ministerul Afacerilor Interne (Ministry of Internal Affairs)
|RO
|iso6523-actorid-upis::9991:ro000000005
|
|
|
|
|
|DE,DR

DO,DT
|DE,DR

DO,DT
|
|-
|ORNC
|Oficiul National B22 al Registrului Comertului
|RO
|iso6523-actorid-upis::9991:ro000000006
|
|
|
|DE,DR

DO,DT
|DE,DR

DO,DT
|
|
|
|-
|BVE
|Bolagsverket (Companies Registration Office)
|SE
|iso6523-actorid-upis::9991:se000000013
|
|
|
|DE,DR
|DE,DR
|
|
|
|-
|JSI
|Institut "Jožef Stefan" (Jožef Stefan Institute)
|SI
|iso6523-actorid-upis::9949:si55560822
|
|DE
|
|
|
|
|
|
|-
|MIZŠ
|Ministrstvo za izobraževanje, znanost in šport (Ministry of Education, Science and Sport)
|SI
|iso6523-actorid-upis::9949:si14246821
|DE
DO
|
|DC
DP
|
|
|
|
|*The central preview functionality for DO is provided by SI-MPA.
|-
|SI-MPA
|Ministrstvo za javno upravo (Ministry of Public Administration)
|SI
|iso6523-actorid-upis::9991:si000000015
|DR
DT
|DR
|
|
|
|DR
DT
|DR
DT
|
|-
|MNZ
|Ministrstvo za notranje zadeve (Ministry of the Interior)
|SI
|iso6523-actorid-upis::9949:si52817652
|
|
|
|
|
|DO
|DO
|*The central preview functionality for DO is provided by SI-MPA.
|}

=== Technical information on participants IT2 ===
{| class="wikitable"
!
==== Test domain (Playground) ====
!
==== Pilot domain ====
|-
|
{| class="wikitable"
! colspan="4" |SMP
|-
|'''Country'''
|'''Participant'''
|'''SMP endpoint'''
|'''SMP certificate'''
|-
|ES (shared)
|SGAD
|[https://de4a.redsara.es/sgad-smp https://de4a.redsara.es/sgad-smp/]
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD owncloud folder]
|-
|NL
|RVO
|https://acc-eidas.minez.nl/de4a-smp/
|
|}
|
{| class="wikitable"
! colspan="4" |SMP
|-
|'''Country'''
|'''Participant'''
|'''SMP endpoint'''
|'''SMP certificate'''
|-
|AT
|BRZ
|https://de4a-smp.usp.gv.at/
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD&fileid=1169370 owncloud folder]
|-
|ES
|SGAD
|
|
|-
|LU
|
|
|
|-
|NL
|RVO
|https://acc-eidas.minez.nl/de4a-smp/
|
|-
|PT
|AMA
|[https://pprsmp.iap.gov.pt/ https://pprsmp.iap.gov.pt/smp.iap.gov.pt]
|
|-
|RO
|MOAI
|https://de4a-smp.mai.gov.ro:8443/
|
|-
|SE
|
|
|
|-
|SI
|SI-MPA
|https://toop-smp.pprod.medius.si/public
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SI-MPA owncloud folder]
|}
|-
|
{| class="wikitable"
! colspan="3" |DE
|-
|'''Participant'''
|'''Evidence types consumed'''
|'''DE e-procedure portal'''
|-
|BMDW
|Company Registration
|
|-
|SGAD
|Birth Evidence
Marriage Evidence
|https://pre-as4gw-dt-de4a.redsara.es/de4a-evaluator/
|-
|UJI
|Higher Education Diploma
|
|-
|CTIE
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|RVO
|Company Registration
|
|-
|INESC-ID
|Higher Education Diploma
Secondary Education Diploma
|
|-
|
|
|
|-
|MoAI
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|ORNC
|Company Registration
|
|-
|BVE
|Company Registration
|
|-
|JSI
|Higher Education Diploma
Large Family Evidence

Disability Evidence
|https://grants.e5.ijs.si/grants/public/
|-
|MIZŠ
|Higher Education Diploma
Secondary Education Diploma
|http://srvas2.rrc.si/prijava/?lang=en
|}
|
{| class="wikitable"
! colspan="3" |DE
|-
|'''Participant'''
|'''Evidence types consumed'''
|'''DE e-procedure portal'''
|-
|BMDW
|Company Registration
|
|-
|SGAD
|Birth Evidence
Marriage Evidence
|
|-
|UJI
|Higher Education Diploma
|
|-
|CTIE
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|RVO
|Company Registration
|https://mijn.rvo.nl/digital-europe-for-all-pilot

(production)
|-
|INESC-ID
|Higher Education Diploma
Secondary Education Diploma
|
|-
|
|
|
|-
|MoAI
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|ORNC
|Company Registration
|
|-
|BVE
|Company Registration
|
|-
|JSI
|Higher Education Diploma
Large Family Evidence

Disability Evidence
|
|-
|MIZŠ
|Higher Education Diploma
Secondary Education Diploma
|
|}
|-
|
{| class="wikitable"
! colspan="3" |DO
|-
|'''Participant'''
|'''Evidence types provided'''
|'''DO evidence portal'''
|-
|BMDW
|Company Registration
|
|-
|SGAD
|Higher Education Diploma
Secondary Education Diploma

Large Family Evidence

Disability Evidence

Domicile Registration Evidence

Birth Evidence

Marriage Evidence

Pension Evidence

Unemployment Evidence

Working Life Evidence
|Direct public access is not enabled
|-
|CTIE
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|RVO
|Company Registration
|
|-
|AMA-IP
|Domicile Registration Evidence
|
|-
|INESC-ID
|Higher Education Diploma
|
|-
|MoAI
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|ORNC
|Company Registration
|
|-
|MIZŠ
|Higher Education Diploma
|Direct public access is not enabled
|-
|MNZ
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|Direct public access is not enabled
|}
|
{| class="wikitable"
! colspan="3" |DO
|-
|'''Participant'''
|'''Evidence types provided'''
|'''DO evidence portal'''
|-
|BMDW
|Company Registration
|
|-
|SGAD
|Higher Education Diploma
Secondary Education Diploma

Large Family Evidence

Disability Evidence

Domicile Registration Evidence

Birth Evidence

Marriage Evidence

Pension Evidence

Unemployment Evidence

Working Life Evidence
|
|-
|CTIE
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|RVO
|Company Registration
|
|-
|AMA-IP
|Domicile Registration Evidence
|
|-
|INESC-ID
|Higher Education Diploma
|
|-
|MoAI
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|ORNC
|Company Registration
|
|-
|MIZŠ
|Higher Education Diploma
|Direct public access is not enabled
|-
|MNZ
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|Direct public access is not enabled
|}
|-
|
{| class="wikitable"
! colspan="3" |DR
|-
|'''Participant'''
|'''AS4 certificate'''
|'''Connector endpoint'''
|-
|BRZ
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD&fileid=1169370 owncloud folder]
|https://de4a.usp.gv.at/ado/phase4
|-
|SGAD
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD owncloud folder]
|https://pre-as4gw-dt-de4a.redsara.es/de4a-it2-connector/
|-
|CTIE
|
|
|-
|RVO
|
|[https://acc-eidas.minez.nl/de4a-connector/requestTransferEvidenceIM https://acc-eidas.minez.nl/de4a-connector/]

(iteration 2 version, but DE and DO are still it1 voor IM)
|-
|AMA-IP
|
|http://130.61.108.235/de4a-connector-it2/
|-
|ORNC
|
|
|-
|BVE
|
|
|-
|SI-MPA
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SI-MPA owncloud folder]
|https://toop-as4.pprod.medius.si/
|-
|RO-MOAI
|https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/RO-MOAI&fileid=1173820
|https://de4a.mai.gov.ro:8443/
|}
|
{| class="wikitable"
! colspan="3" |DR
|-
|'''Participant'''
|'''AS4 certificate'''
|'''Connector endpoint'''
|-
|SGAD
|
|
|-
|CTIE
|
|
|-
|RVO
|
|[https://eidas.minez.nl/de4a-connector/requestTransferEvidenceIM https://eidas.minez.nl/de4a-connector/]

(Still Iteration 1 version)
|-
|AMA-IP
|
|http://130.61.108.235/de4a-connector-it2/
|-
|ORNC
|
|
|-
|BVE
|
|
|-
|SI-MPA
|
|
|}
|-
|
{| class="wikitable"
! colspan="3" |DT
|-
|'''Participant'''
|'''AS4 certificate'''
|'''Connector endpoint'''
|-
|BRZ
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD&fileid=1169370 owncloud folder]
|https://de4a.usp.gv.at/ado/phase4
|-
|SGAD
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD owncloud folder]
|https://pre-as4gw-dt-de4a.redsara.es/de4a-it2-connector/
|-
|CTIE
|
|
|-
|RVO
|
|[https://acc-eidas.minez.nl/de4a-connector/requestTransferEvidenceIM https://acc-eidas.minez.nl/de4a-connector/]
|-
|AMA-IP
|
|http://130.61.108.235/de4a-connector-it2/
|-
|MoAI
|
|
|-
|ORNC
|
|
|-
|SI-MPA
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SI-MPA owncloud folder]
|https://toop-as4.pprod.medius.si/
|}
|
{| class="wikitable"
! colspan="3" |DT
|-
|'''Participant'''
|'''AS4 certificate'''
|'''Connector endpoint'''
|-
|BRZ
|
|
|-
|SGAD
|
|
|-
|CTIE
|
|
|-
|RVO
|
|[https://eidas.minez.nl/de4a-connector/requestTransferEvidenceIM https://eidas.minez.nl/de4a-connector/]

(Still Iteration 1 version)
|-
|AMA-IP
|
|http://130.61.108.235/de4a-connector-it2/
|-
|MoAI
|
|
|-
|ORNC
|
|
|-
|SI-MPA
|
|
|}
|}

===DE-DO.json participant endpoint urls===
{| class="wikitable"
!
====Test domain (PRE2b) ====
!
====Pilot domain (PRO2)====
|-
|
{| class="wikitable"
! colspan="5" |Data Owners
|-
|'''Country'''
|'''Participant'''
|'''Participant ID'''
|'''Pattern'''
|'''DO Endpoint URL'''
|-
| rowspan="4" |AT
| rowspan="4" |
| rowspan="4" |iso6523-actorid-upis::99XX:at000000271-test-it2
|IM
|
|-
|USI
|
|-
| LU
|
|-
|SN
|
|-
| rowspan="4" | ES
| rowspan="4" |SGAD
| rowspan="4" |iso6523-actorid-upis::9920:ess2833002e-test-it2
|IM
|https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/requestExtractEvidenceIM
|-
|USI
|https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/do1/usi/extractevidence
|-
|LU
|https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/dataOwner/in/lu/
|-
|SN
|https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/dataOwner/in/sn/
|-
| rowspan="4" |PT
| rowspan="4" |AMA
| rowspan="4" | iso6523-actorid-upis::99XX:pt000000026-test-it2
|IM
|
|-
|USI
|
|-
| LU
|
|-
|SN
|
|-
| rowspan="4" |NL
| rowspan="4" |RVO
| rowspan="4" |iso6523-actorid-upis::9999:nl000000106-test-it1
|IM
|
|-
|USI
|
|-
|LU
|
|-
|SN
|
|-
| rowspan="4" |SI
| rowspan="4" |MIZŠ
| rowspan="4" |iso6523-actorid-upis::9949:si14246821
|IM
|N/A
|-
|USI
|Not publicly disclosed
|-
|LU
|N/A
|-
|SN
|N/A
|-
|SI
|MNZ
|iso6523-actorid-upis::9949:si52817652
|USI
|Not publicly disclosed
|-
| rowspan="4" |SE
| rowspan="4" |BVE
| rowspan="4" |iso6523-actorid-upis::99XX:se000000013-test-it2
|IM
|
|-
|USI
|
|-
|LU
|
|-
|SN
|
|}
{| class="wikitable"
! colspan="5" |Data Evaluators
|-
|'''Country'''
|'''Participant'''
|'''Participant ID'''
|'''Response Type'''
|'''DE Endpoint URL'''
|-
| rowspan="4" | AT
| rowspan="4" |
| rowspan="4" |iso6523-actorid-upis::99XX:at000000271-test-it2
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" |ES
| rowspan="4" |SGAD
| rowspan="4" |iso6523-actorid-upis::9920:ess2833002e-test-it2
|response
|https://pre-as4gw-dt-de4a.redsara.es/de4a-evaluator/response/requestForwardEvidence
|-
|subscription_resp
|N/A
|-
|redirect
|https://pre-as4gw-dt-de4a.redsara.es/de4a-evaluator/response/usiRedirectUser
|-
|notification
|N/A
|-
| rowspan="4" | ES
| rowspan="4" |UJI
| rowspan="4" |iso6523-actorid-upis::9920:esq6250003h-test-it2
|response
|
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |PT
| rowspan="4" | INESC-ID
| rowspan="4" |iso6523-actorid-upis::9991:pt990000101-test-it2
|response
|
|-
|subscription_resp
| N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |NL
| rowspan="4" |RVO
| rowspan="4" |iso6523-actorid-upis::99XX:nl000000024-test-it1
|response
|N/A
|-
|subscription_resp
| N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |MIZŠ
| rowspan="4" |iso6523-actorid-upis::9949:si14246821
|response
|http://srvas2.rrc.si/de4a/requestForwardEvidence
|-
|subscription_resp
|N/A
|-
|redirect
|http://srvas2.rrc.si/de4a/redirectUser
|-
|notification
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |JSI
| rowspan="4" |iso6523-actorid-upis::9949:si55560822-test-it2
| response
| https://grants.e5.ijs.si/grants/public/de-r/requestForwardEvidence
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |SE
| rowspan="4" |BVE
| rowspan="4" |iso6523-actorid-upis::99XX:se000000013-test-it2
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|}
|
{| class="wikitable"
! colspan="5" |Data Owners
|-
|'''Country'''
|'''Participant'''
|'''Participant ID'''
|'''Pattern'''
|'''DO Endpoint URL'''
|-
| rowspan="4" |AT
| rowspan="4" |
| rowspan="4" |
|IM
|N/A
|-
|USI
|N/A
|-
| LU
|N/A
|-
|SN
|N/A
|-
| rowspan="4" | ES
| rowspan="4" |SGAD
| rowspan="4" |
|IM
|N/A
|-
|USI
|N/A
|-
|LU
|N/A
|-
|SN
|N/A
|-
| rowspan="4" |PT
| rowspan="4" |AMA
| rowspan="4" |
|IM
| N/A
|-
|USI
|N/A
|-
| LU
| N/A
|-
|SN
|N/A
|-
| rowspan="4" |NL
| rowspan="4" |RVO
| rowspan="4" |so6523-actorid-upis::9991:nl000000106-it1
|IM
|N/A
|-
|USI
|N/A
|-
|LU
|N/A
|-
|SN
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |MIZŠ
| rowspan="4" |iso6523-actorid-upis::9949:si14246821
|IM
|N/A
|-
|USI
|Not publicly disclosed
|-
|LU
|N/A
|-
|SN
|N/A
|-
|SI
|MNZ
|iso6523-actorid-upis::9949:si52817652
|USI
|Not publicly disclosed
|-
| rowspan="4" |SE
| rowspan="4" |BVE
| rowspan="4" |
|IM
|N/A
|-
|USI
|N/A
|-
|LU
|N/A
|-
|SN
|N/A
|}
{| class="wikitable"
! colspan="5" |Data Evaluators
|-
|'''Country'''
|'''Participant'''
|'''Participant ID'''
|'''Response Type'''
|'''DE Endpoint URL'''
|-
| rowspan="4" | AT
| rowspan="4" |
| rowspan="4" |
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" |ES
| rowspan="4" |SGAD
| rowspan="4" |
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" | ES
| rowspan="4" |UJI
| rowspan="4" |
|response
|
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |PT
| rowspan="4" | INESC-ID
| rowspan="4" |
|response
|
|-
|subscription_resp
| N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |NL
| rowspan="4" |RVO
| rowspan="4" |iso6523-actorid-upis::9991:nl000000024-it1
|response
|N/A
|-
|subscription_resp
| N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |MIZŠ
| rowspan="4" |iso6523-actorid-upis::9949:si14246821
|response
|
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |JSI
| rowspan="4" |iso6523-actorid-upis::9949:si55560822
| response
|
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |SE
| rowspan="4" |BVE
| rowspan="4" |
|response
| N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|}

|}

==DE4A infrastructure IT2==
===Playground infrastructure IT2===
The following diagram depicts the Playground infrastructure for the second iteration, with the deployment of its corresponding components.[[File:DE4A network IT2-Playground IT2.drawio.png|frame|alt=|none]]

===Pilot partners infrastructure flavours IT2 ===
The following two diagrams outline the general infrastructure expected from the Member States and partners involved in the pilots. Each Connector is in turn connected and exchanges data with the corresponding Connector (DR or DT) of the Playground or other partners.

At this stage, all DE4A participants are expected to follow the set-up A, while only Romania is expected to follow set-up B.[[File:DE4A network IT2-Country set-up A.drawio.png|frame|alt=|left]]

[[File:DE4A network IT2-Country set-up B.drawio.png|frame|alt=|none]]

== Domains and types of participant IDs ==

===DE4A domains===
In DE4A, there are two types of participants:

*Imaginary participants: intended to query the examples stored in the Mocked DO.
*Real participants: intended to retrieve data directly returned by partners.

At the same time, for the real participants, there are also two “domains”:

*Test domain: only fake data is used for test purposes. It is the domain related to the DE4A Playground, where participants return datasets from test sources.
*Pilot domain: real data from real citizens and companies is supposed to be used. It is the environment used for the running phase of the pilots, where participants access to their real registries and return real evidence from them.

Finally, the project is divided into two iterations where each of them needs a copy of those two domains, and where some overlap between them occurs.
[[File:Domain overlap.png|none|thumb|910x910px]]
As the DE4A project uses the dynamic discovery of eDelivery, where there cannot be duplicate participant IDs targeting to different Connectors (depending on the domain concerned), we need to define a different participant ID schema per each domain:

*'''PRE1a''': Imaginary participants stored in the Mocked DO for iteration 1 for testing. The related evidence is stored in the Mocked DO deployed in SGAD (ES).
** Scheme identifier used: “'''9999'''”.
** Suffix used: “'''-it1'''”.
**E.g. iso6523-actorid-upis::99'''99''':ess2833002e'''-it1'''

*'''PRE1b:''' Simulated data returned by the real participants used for testing in Playground iteration 1. The related evidence is located in each partner’s infrastructure, within their test domain.
**Scheme identifier used: “'''99XX'''”, where “XX” depends on the identifier each participant is using.
**Suffix used: “'''-it1'''”.
**E.g. iso6523-actorid-upis::99'''20''':ess2833002e'''-it1'''
*'''PRO1:''' Real data returned by the real participants during the execution of phase 1 of the pilot. The related evidence is located in each partner’s infrastructure, within their pilot domain.
**Scheme identifier used: “'''99XX'''”, where “XX” depends on the identifier each participant is using. It is the “real” participant ID.
**Suffix used: ''none'', since there is no overlap between phases 1 and 2 of the pilots.
**E.g. iso6523-actorid-upis::99'''20''':ess2833002e
*'''PRE2a:''' Imaginary participants stored in the Mocked DO for iteration 2 for testing. The related evidence is stored in the Mocked DO deployed in SGAD (ES).
**Scheme identifier used: “'''9999'''”.
**Suffix used: “'''-mock-it2'''”.
**E.g. iso6523-actorid-upis::99'''99''':ess2833002e'''-mock-it2'''
*'''PRE2b:''' Simulated data returned by the real participants used for testing in Playground iteration 2. The related evidence is located in each partner’s infrastructure, within their test domain.
**Scheme identifier used: “'''99XX'''”, where “XX” depends on the identifier each participant is using.
**Suffix used: “'''-test-it2'''”.
**E.g. iso6523-actorid-upis::99'''20''':ess2833002e'''-test-it2'''
*'''PRO2:''' Real data returned by the real participants during the execution of phase 2 of the pilot. The related evidence is located in each partner’s infrastructure, within their pilot domain.
**Scheme identifier used: “'''99XX'''”, where “XX” depends on the identifier each participant is using. It is the “real” participant ID.
**Suffix used: ''none'', since there is no overlap between phases 1 and 2 of the pilots.
**E.g. iso6523-actorid-upis::99'''20''':ess2833002e

Therefore, DE4A domains are differentiated by the participant ID schema used.

===Location of the participant IDs===
These different participant IDs must be stored in their corresponding IDKs and SMPs and configured to return the proper information:

*'''PRE1a:''' Imaginary participants
**IDK: none (for these participants, the mocked DE knows which the imaginary participants are and which DO to query, namely, the mocked DO of the first iteration).
**SMP: shared SMP of the Playground IT1. It returns the routing information of the targeted Connector (DR/DT) of the Playground IT1.
*'''PRE1b''': Simulated data from real participants
**IDK: mocked IDK of the Playground IT1.
**SMP: shared SMP of the Playground IT1. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.
*'''PRO1:''' Real data from real participants
**IDK: mocked IDK of the pilot running environment.
**SMP: national SMP of the requested participant. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.
***For the first pilot running phase, partners who have not yet deployed their own SMPs will be able to use a shared SMP provided by one of the partners with an available SMP. In such cases, the routing information of those partners will be stored in this shared SMP.
*'''PRE2a:''' Imaginary participants
**IDK: Central IAL. Its information is automatically updated and fed from the SMPs connected to it.
**SMP: shared SMP of the Playground IT2. It returns the routing information of the targeted Connector (DR/DT) of the Playground IT2.
*'''PRE2b:''' Simulated data from real participants
**IDK: Central IAL. Its information is automatically updated and fed from the SMPs connected to it.
**SMP: national SMP of the requested participant. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.
*'''PRO2:''' Real data from real participants
**IDK: Central IAL. Its information is automatically updated and fed from the SMPs connected to it.
**SMP: national SMP of the requested participant. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.

DE4A Connector it2

2022-11-15T09:24:15Z

Javier.ferrero: Quality review

The DE4A Connector is a technical proxy that allows the final participants (DE or DO) to send requests for evidence or responses to other final participants over an [[Usage of third party specifications and components|eDelivery]] communication environment. In addition, to handle the message exchange process, the Connector is responsible for obtaining the message routing information, by exchanging information with external components such as the Central IAL, the [[Usage of third party specifications and components|SML/DNS]] or the [[SMP]].

To do so, it provides a common interface to DEs and DOs, making the complexity of the system transparent to the final participants and integration easier.

The Connector component provides the [[AS4 Gateway]] functionality, so it can assume both the role of Data Requestor and Data Transferor. This approach makes the Connector a stand-alone web application that can be deployed on any suitable application server.

The security and integrity of messages, as well as the unique identification of the participants involved, are the cornerstones of the Connector component.[[File:DE4A network IT2 v2-Target infrastructure it2.drawio.png|alt=|center|frame|Conceptual schema of the target DE4A system for the second iteration.]]

== Functionalities provided ==
The main purpose of the DE4A Connector is sending and receiving evidence requests and their responses. The message exchange process is described in the DE4A deliverables D2.4 Project Start Architecture and D5.3 Initial technical design of interfaces.

=== Routing information lookup ===
The DE4A Connector is responsible for obtaining the Data Provider information from the [[DE4A Issuing Authority Locator (IAL)|Central IAL]]. The Central IAL collects information from all the SMPs deployed at each partner infrastucture and offers it in a centralized way through the REST API <code>/lookupRoutingInformation</code>. When queried about a Canonical Item (Evidence or Event Catalogue) and a country, it returns the identifier of the Data Owner to request that Canonical Item from in that country. Therefore, through this functionality, the DE4A Connector implements the [[DE4A Issuing Authority Locator (IAL)|IAL]] semantic tool.

=== Dynamic discovery of services ===
In order for the Connector to be able to send a message to the corresponding endpoint, the [[Usage of third party specifications and components|eDelivery]] dynamic discovery mode of operation is used. This operation mode is based on the use of the components of the eDelivery infrastructure: [[Usage of third party specifications and components|SML/DNS]] and SMPs. Through this functionality, the DE4A Connector implements the [[DE4A Evidence Service Locator (ESL)|ESL]] semantic tool.

The main elements stored in the SML/DNS and SMPs for this purpose are the following:

* ''ParticipantIdentifier'': The Data Owner/Data Evaluator identifier who is publishing its [[Usage of third party specifications and components|AS4]] communication point (or the Connector linked to it).
* ''DocumentTypeIdentifier'': Canonical Evidence Type or Canonical Event Catalogue.
* ''ProcessIdentifier'': Orchestration type: request, response or notification.
* ''AS4'' endpoint: AS4 service endpoint URL.
* ''Certificate'': The X.509 certificate of the AS4 server, used to encrypt the transmitted data for this specific participant.

The information described above is managed by the SML/DNS and SMP components and is used by the Connector when working with the phase4 implementation of AS4.

Focusing on the SML/DNS/SMP data retrieval, the process will take place according to the following features:

* SSL/TLS communication is mandatory.
* Response signature validation is mandatory.
* The communication between SMP and SML requires the usage of a client certificate.
The service metadata lookup will be performed as a step prior to the [[Usage of third party specifications and components|AS4]] message exchange. Therefore, the participant IDs and other related information must be known by the DE4A Connector in advance.

=== Supported interaction patterns ===
Interaction patterns define the flow of data through the Connector and the intercommunication between the different components. Each pattern exchanges certain types of messages, and the incoming/outgoing information will depend on the processes occurring in the external components.

The Connector currently supports four interaction patterns: [[Intermediation Pattern|Intermediation (IM)]], [[User-supported Intermediation Pattern|User-Supported intermediation (USI)]], [[Subscription and Notification Pattern|Subscription and Notification (S&N)]] and [[Lookup Pattern|Lookup (LU)]] patterns. The [[Verifiable Credentials Pattern|Verifiable Credentials (VC)]] pattern is not supported by the DE4A Connector since that interaction pattern has benn implemented through its own components: the [[DE4A SSI Authority Agent|SSI Authority Agent]] and the [[DE4A SSI Edge Agent|SSI Edge Agent]].

Most of the specific behaviour of each interaction pattern is independent of the Connector itself, as the Connector component is just designed to exchange messages and the main differences between the patterns take place in the external components such as the Data Evaluator and the Data Owner.

Additionally, the DE4A Connector offers a '''backwards compatibility feature''' for the former synchronous IM pattern. It can handle the old messaging structure, so the synchronous implementation is fully compatible with the current asynchronous version.

=== Connector roles ===
A Connector instance can play two different roles:

* Data Requestor (DR)
* Data Transferor (DT)

No configuration is needed to differentiate the roles, it only depends on the usage, i.e., the behaviour will be according to the messages sent. Moreover, in a functional scenario, the SMP data will determine which Connector is playing the DR or DT role.

=== AS4 implementations ===
The message exchange is built on the [[Usage of third party specifications and components|AS4]] protocol, which is an open standard for secure, payload-agnostic, business-to-business document exchange via web services. Secure document exchange is governed by WS-Security aspects, including XML Encryption and XML Digital Signatures.

==== phase4 ====
The DE4A Connector implements phase4 as a gateway to perform the AS4 message exchange.
* '''Main features'''
** It is a generic AS4 solution.
** It can be integrated in basically any Servlet-based application server.
** It can easily be used with Peppol.
** It can be used with other Dynamic Discovery solutions.
** It supports a high degree of customization.
** It is not limited to the CEF/e-SENS profile.

All necessary configuration parameters are provided by the properties file of the DE4A Connector.

=== Error handling ===
Since the Connector performs multiple communications between different external components and some data and structure validations are performed, the Connector needs to monitor all failure points and be able to identify them in order to build the corresponding messages and warnings to inform each external component. When an error happens, the corresponding component creates an error message with the information about the error to be sent back to the entity that sent the failed message.

The error handling is based on the set of [[DE4A Logs and error messages it2|log and error messages]] defined for DE4A.

=== Kafka messages ===
Within the data flow and message exchange, there are many key points where it is important to know how the data is being managed, as well as identifying intermediate errors and unhandled system states. In this respect, the Connector can send messages to a [[Usage of third party specifications and components|Kafka]] server to track the data flow and trace the state of the system at certain points.

This feature is an advantage from a technical and business point of view, as the Connector performs the message exchange transparently to the other components.

It should be noted that the messages sent to the Kafka server are hardcoded, it is not a parameterizable feature, so any enhancements must be hardcoded again and deployed. It has been developed in such a way because the necessity of a Kafka server is not expected outside the DE4A project. In a real scenario, an alternative way of collecting logs should be implemented.

==== Message types ====
The Connector implements a [[Usage of third party specifications and components|Kafka]] message producer through the de4a-kafka-client library of the de4a-commons package. This producer provides several types of messages or severity levels:

* '''Success'''
* '''Info'''
* '''Warn'''
* '''Error'''
* '''Fatal error'''

Those message categories can be easily used to specify the severity level of the message sent to the Kafka server to track and identify them.

==== List of messages ====
The messages currently sent from the Connector to the Kafka server are as follows:

'''Services''' – ''(Info level)''

* RequestTransferEvidenceIM message received - RequestId: <code>{0}</code>, CanonicalEvidenceType: <code>{1}</code>, DataEvaluator: <code>{2}</code>, DataOwner: <code>{3}</code>
* RequestTransferEvidenceUSI message received - RequestId: <code>{0}</code>, CanonicalEvidenceType: <code>{1}</code>, DataEvaluator: <code>{2}</code>, DataOwner: <code>{3}</code>
* RequestTransferEvidenceUSIDT message received - RequestId: <code>{0}</code>
* RequestLookupRoutingInformation message received - CanonicalEvidenceType: <code>{0}</code>, CountryCode: <code>{1}</code>, DataOwnerId: <code>{2}</code>
* Sending request to IDK - URL: <code>{0}</code>
* Looking for Data Owner address - DataOwnerId: <code>{0}</code>

'''Client''' – ''(Info level)''

* Requesting to SMP - ParticipantId: <code>{0}</code>, DocumentTypeId: <code>{1}</code>, MessageType: <code>{2}</code>
* Sending RequestForwardEvidence to the Data Evaluator - RequestId: <code>{0}</code>, DataEvaluatorId: <code>{1}</code>, DataOwnerId: <code>{2}</code>, Endpoint: {3}
* Sending RequestExtractEvidence IM to the Data Owner - RequestId: <code>{0}</code>, CanonicalEvidenceType: <code>{1}</code>, DataEvaluatorId: <code>{2}</code>, DataOwnerId: <code>{3}</code>, Endpoint: <code>{4}</code>
* Sending RequestExtractEvidence USI to the Data Owner - RequestId: <code>{0}</code>, CanonicalEvidenceType: <code>{1}</code>, DataEvaluatorId: <code>{2}</code>, DataOwnerId: <code>{3}</code>, Endpoint: <code>{4}</code>

'''AS4''' – ''(Info level)''

* Sending request message via AS4 gateway - DataEvaluatorId: <code>{0}</code>, DataOwnerId: <code>{1}</code>, CanonicalEvidenceType: <code>{2}</code>
* Sending response message via AS4 gateway - DataEvaluatorId: <code>{0}</code>, Message tag: <code>{1}</code>, CanonicalEvidenceType: <code>{2}</code>
* Processing the request received via AS4 gateway - RequestId: <code>{0}</code>
* Processing the response received via AS4 gateway - RequestId: <code>{0}</code>

'''Errors''' – ''(Error level)''

* The corresponding request to the received response is not found on database - RequestId: <code>{0}</code>
* RequestForwardEvidence has not been sent, unknown Data Evaluator endpoint - RequestId: <code>{0}</code>, DataEvaluatorId: <code>{1}</code>
* RequestTransferEvidence not found on AS4 incoming message
* Error processing incoming message from AS4 gateway
* Error building URI from Data Evaluator endpoint: <code>{0}</code>
* Error sending message to Data Requestor via AS4 gateway - RequestId: <code>{0}</code>
* Data Owner address not found - DataOwnerId: <code>{0}</code>
[1] The <code>{x}</code> symbols are placeholders for dynamic text to be logged.

===Data management===
The Connector stores and manages certain information such as DE endpoints (not to be confused with SMP endpoints), DO endpoints, certain request records for asynchronous response matching, etc. All this data and where to find it is described in the following subsections.

====Data Owner and Data Evaluator addresses====
Once each Data Owner is publishing his Connector service information on the SMP, the request will arrive to that Connector service configured on the SMP (via the AS4 Gateway), and considering that one Connector could be serving to multiples DOs, this Connector has to know the addressing (base endpoint, without path name) information related to a specific participant identifier (e.g. iso6523-actorid-upis::9999:egov) to send forward the request to the corresponding Data Owner, so due to that, the Connector has a configuration file '''de-do.json''' where the information for the data owner and/or the Data Evaluator endpoints is stored. More information is available at [[Connector iteration 2 installation and configuration guide]].
==Security==
The message exchange performed by the Connector has been conceived to ensure different security aspects as:

*'''Authenticity''': ensures the identity of the participant entities and any common component involved in the message exchange. It is achieved through the participant identifiers definition, [[Usage of third party specifications and components|eDelivery]] specification and [[Usage of third party specifications and components|AS4]] implementations.

* '''Integrity''': refers to the accuracy and completeness of data. Security controls focused on integrity are used to prevent data from being modified or misused by an unauthorized party, provided by the WS-security and XML message signature.

*'''Confidentiality''': data confidentiality at message level could be achieved by taking advantage of WS-Security encryption feature in User messages. This message encryption is performed via asymmetric keys: the sender of the message encrypts with the public key of the recipient, so the message can only be decrypted by the recipient, who owns the private key. Those keys should be configured either in the Connector in case of phase4 or in any external AS4 gateway.

===Communications===
The Connector creates a secure context to establish in/outgoing connections with external components.

The main elements for such communication securitisations are:

*'''Private key''': private part of private-public key pair used in the TLS handshake between your server and the connecting clients. This private key must be configured in the Connector properties in order to create the secure context as well in the web server, in the case of reverse proxy or any similar structure. The keys configured on each component are generated under the DE4A management.

*'''Truststore''': used for the storage of certificates from the trusted Certificate Authority (CA), which is used in the verification of the certificate provided by the server in an SSL connection. The Connector provides a default truststore which allows to trust on certificates generated under the main DE4A CA.

====HTTP Proxy mode====
Sometimes, the environments have certain communication structure where the outgoing connections must be performed through an HTTP proxy server. The Connector provides de functionality and proper configuration to perform the communications via an HTTP proxy server.
===Message cryptographic protection ===
The Connector messages exchange can be separated into:

====REST APIs messages====
Once the SSL connection is established, all the data exchanged through it, will be encrypted on transport level based on the SSL context configuration settled, either managed by a reverse proxy on the server environment or configuring the proper application properties.

====AS4 messages====

*'''Phase4''': internally the message is encrypted using a specific keystore configuration only used for this purpose; also the cross-gateways communications are additionally encrypted over the HTTPS secure protocol.

===Message validation===
Message validation is performed at different stages of the Connector data flow, from message structure compliance to content integrity.

====Schema validation====
All the messages produced and consumed by the Connector are performing an XML Schema validation once it is received or sent out. This validation is done by the object conversion library that keeps the schema model including all the structure and content constraints.

====Signature validation====
As well as the XML Schema validation, the Connector performs validations to ensure the content and reliability on certain phases of the message exchange process:

*Services metadata querying
*In the SMP data exchange a message signature validation is being performed to maintain the content reliability. This validation consists of verifying the embedded signature on the message against the trust certificate configured in the Connector for that purpose.
The signature of incoming AS4 messages is verified against the central [[Usage of third party specifications and components|AS4]] Gateway CA globally used in DE4A project, internally validated by the implementation libraries that handle the reception and delivery.

==Technology used==

===System core architecture===
The Connector works as standalone application that runs different web services according to the RESTful API architecture principles. The application is built with the following tools:

*Spring Framework version 5.x.
*Java 11
*Apache HTTP Client 4.x

In addition to the core architecture, the XML Schemas defined to model the exchanged information, data constraints, interfaces, etc. are also important. All this is part of the Connector core through the de4a-commons library, which contains the above-mentioned model as well as utilities and conversion tools.

*Author: ''DE4A (WP5)''
*Repository: https://github.com/de4a-wp5/de4a-commons

===Third party libraries===
As part of the bunch of libraries used by the Connector there are some of the related with the core features and which represent a starting point for the functionalities provided by the Connector.

==== TOOP Connector====
The TOOP Connector is a set of shared utility functions used in the Connector to perform common tasks that are required for a safe and interoperable data exchange. In the initial iteration the latest version of the TOOP Connector technical components were reused mainly for the usage of the built-in phase4 AS4 Gateway. Other elements of the TOOP Connector are currently ignored.

*Author: ''TOOP Project''
*Repository: https://github.com/de4a-wp5/toop-connector-ng

====ph-oton libraries====
Set of Java libraries to build Java web applications.

*Author: ''Philip Helger (phax)''
*Repository: https://github.com/phax/ph-oton

====Peppol commons libraries====
They include the SMP client library used by the Access Points to retrieve service metadata. This library supports the Peppol SMP specification, the OASIS BDXR SMP v1 and OASIS BDXR SMP v2 specification. This project uses Apache HTTP client to perform the REST lookups on foreign SMPs.

*Author: ''Philip Helger (phax)''
*Repository: https://github.com/phax/peppol-commons

=== Data management===
To manage the model and the data stored by the Connector the following technologies are used:

*'''JPA:''' The Java Persistence API is a specification of Java. It is used to persist data between Java object and relational database. JPA acts as a bridge between object-oriented domain models and relational database systems. As JPA is just a specification, it does not perform any operation by itself.

*'''Hibernate:''' An object–relational mapping tool for the Java programming language. It provides a framework for mapping an object-oriented domain model to a relational database. Hibernate handles object–relational impedance mismatch problems by replacing direct, persistent database accesses with high-level object handling functions.

===Utilities libraries===
The project uses several libraries and utilities to process and transform the data. They can be divided according to their nature:

*'''Commercial libraries'''

To perform common and non-business operations on web and data exchange projects, the Connector uses different commercial solutions, also all the libraries embedded in the Java development kit.

*'''In-house solutions'''
The Connector project includes some utilities that allow the data processing and internal tools to perform all the Connector tasks. Those utilities are within the Connector project as a module called ''de4a-commons.''
[[Category:Wip]]

DE4A Connector it2

2022-11-14T16:51:34Z

Javier.ferrero: Minor fixes

The DE4A Connector is a technical proxy that allows the final participants (DE or DO) to send requests for evidence or responses to other final participants over an [[Usage of third party specifications and components|eDelivery]] communication environment. In addition, to handle the message exchange process, the Connector is responsible for obtaining the message routing information, by exchanging information with external components such as the Central IAL, the [[Usage of third party specifications and components|SML/DNS]] or the [[SMP]].

To do so, it provides a common interface to DEs and DOs, making the complexity of the system transparent to the final participants and integration easier.

The Connector component provides the [[AS4 Gateway]] functionality, so it can assume both the role of Data Requestor and Data Transferor. This approach makes the Connector a stand-alone web application that can be deployed on any suitable application server.

The security and integrity of messages, as well as the unique identification of the participants involved, are the cornerstones of the Connector component.[[File:DE4A network IT2 v2-Target infrastructure it2.drawio.png|alt=|center|frame|Conceptual schema of the target DE4A system for the second iteration.]]

== Functionalities provided ==
The main purpose of the DE4A Connector is sending and receiving evidence requests and their responses. The message exchange process is described in the DE4A deliverables D2.4 Project Start Architecture and D5.3 Initial technical design of interfaces.

=== Routing information lookup ===
The Connector is responsible for obtaining the Data Provider information from the Central IAL. It exposes a REST API <code>/lookupRoutingInformation</code> to get information about the Data Owners that provide a specific Canonical Evidence Type and further related information. That information is used to construct a request message to be sent through the Connector. Thus, the Data Evaluator is the only consumer of the mentioned API method.

=== Dynamic discovery of Services ===
In order for the Connector to be able to send a message to the corresponding endpoint, the [[Usage of third party specifications and components|eDelivery]] dynamic discovery mode of operation is used. This operation mode is based on the use of the [[DE4A Issuing Authority Locator (IAL)|IAL]] and [[Usage of third party specifications and components|SML/DNS]] and SMP components of the eDelivery infrastructure.

The IAL is a new component for it2, it offers centralized information of all the SMPs deployed at each partner infrastucture. When a request is performed to the IAL it gathers the distributed information en each SMP to enroute to the correct destination.

The main elements stored in the SML/DNS and SMPs for this purpose are the following:

* ''ParticipantIdentifier'': The Data Owner/Data Evaluator identifier who is publishing its [[Usage of third party specifications and components|AS4]] communication point (of the Connector linked to it).
* ''DocumentTypeIdentifier'': Canonical evidence type.
* ''ProcessIdentifier'': Orchestration type (request/response).
* ''AS4'' endpoint: AS4 service endpoint URL.
* ''Certificate'': The X.509 certificate of the AS4 server, used to encrypt the transmitted data for this specific participant.

The information described above is managed by the SML/DNS and SMP components and is used by the Connector when working with the phase4 implementation of AS4.

Focusing on the SML/DNS/SMP data retrieval, the process will take place according to the following features:

* SSL/TLS communication is mandatory.
* Response signature validation is mandatory.
* The communication between SMP and SML requires the usage of a client certificate.
The service metadata lookup will be performed as a step prior to the [[Usage of third party specifications and components|AS4]] message exchange. Therefore, the participant IDs and other related information must be known by the Connector in advance.

=== Supported interaction patterns ===
Interaction patterns define the flow of data through the Connector and the intercommunication between the different components. Each pattern exchanges certain types of messages, and the incoming/outgoing information will depend on the processes occurring in the external components [3].

The Connector currently supports three interaction patterns:

* '''Intermediation (IM) pattern'''
** Asynchronous communication between the Connector and final participant (DE or DO).
** Data Owner endpoint must be known by the Data Transferor.
** Since the communication is synchronous, the Data Requestor does not need to know the identifier and endpoint of the Data Evaluator.

* '''User supported intermediation (USI) pattern'''
** Asynchronous communication between the Connector and final participant (DE or DO).
** Data Owner endpoint must be known by the Data Transferor.
** Since the communication is asynchronous, the Data Evaluator endpoint must be known by the Data Requestor. In addition, the Data Evaluator identifier is recovered from the request, since it is not sent in the response from the Data Transferor.

* '''Subscription and Notification (S&N) pattern'''
** Asynchronous communication between the Connector and final participant (DE or DO).
** Data Owner endpoint must be known by the Data Transferor.
** Since the communication is asynchronous, the Data Evaluator endpoint must be known by the Data Requestor. In addition, the Data Evaluator identifier is recovered from the request, since it is not sent in the response from the Data Transferor.

Most of the specific behaviour of each interaction pattern is independent of the Connector itself, as the Connector component is just designed to exchange messages and the main differences between the patterns take place in the external components such as the Data Evaluator and the Data Owner.

Additionally, the it2 connector offers a '''backwards compatibility feature''' for the IM pattern of it1. It can handle old messaging structure so implementation for it1 will be fully compatible with the it2 connector. In it1 IM pattern worked as a synchronous communication, this backwards compatibility also works with synchronous communication.

=== Connector roles ===
A Connector instance can play two different roles:

* Data Requestor (DR)
* Data Transferor (DT)

No configuration is needed to differentiate the roles, it only depends on the usage, i.e., the behaviour will be according to the messages sent.

Also, in a functional scenario the SMP data will determine which Connector is playing the DR or DT role.

=== AS4 implementations ===
The message exchange is built on the [[Usage of third party specifications and components|AS4]] protocol, which is an open standard for secure, payload-agnostic business-to-business document exchange via web services. Secure document exchange is governed by WS-Security aspects, including XML Encryption and XML Digital Signatures.

==== Phase4 ====

* '''Main features'''
** It is a generic AS4 solution.
** It can be integrated in basically any Servlet-based application server.
** It can easily be used with Peppol.
** It can be used with other Dynamic Discovery solutions.
** It supports a high degree of customization.
** It is not limited to the CEF/e-SENS profile.

* '''Implementation'''
** The Connector implements phase4 as a gateway to perform the AS4 message exchange.

All necessary configuration parameters are provided by the properties file of the Connector.

=== Error handling ===
Since the Connector performs multiple communications between different external components and some data and structure validations are performed, the Connector needs to monitor all failure points and be able to identify them in order to build the corresponding messages and warnings to inform each external component. When an error happens, the corresponding component creates an error message with the information about the error to be sent back to the entity that sent the failed message.

=== Kafka messages ===
Within the data flow and message exchange, there are many key points where it is important to know how the data is being managed, as well as identifying intermediate errors and unhandled system states. In this respect, the Connector can send messages to a [[Usage of third party specifications and components|Kafka]] server to track the data flow and trace the state of the system at certain points.

This feature is an advantage from a technical and business point of view, as the Connector performs the message exchange transparently to the other components.

It should be noted that the messages sent to the Kafka server are hardcoded, it is not a parameterizable feature, so any enhancements must be hardcoded again and deployed. It has been developed in such a way because the necessity of a Kafka server is not expected outside the DE4A project. In a real scenario, an alternative way of collecting logs should be implemented.

==== Message types ====
The Connector implements a [[Usage of third party specifications and components|Kafka]] message producer through the de4a-kafka-client library of the de4a-commons package. This producer provides several types of messages or severity levels:

* '''Success'''
* '''Info'''
* '''Warn'''
* '''Error'''
* '''Fatal error'''

Those message categories can be easily used to specify the severity level of the message sent to the Kafka server to track and identify them.

==== List of messages ====
The messages currently sent from the Connector to the Kafka server are as follows:

'''Services''' – ''(Info level)''

* RequestTransferEvidenceIM message received - RequestId: <code>{0}</code>, CanonicalEvidenceType: <code>{1}</code>, DataEvaluator: <code>{2}</code>, DataOwner: <code>{3}</code>
* RequestTransferEvidenceUSI message received - RequestId: <code>{0}</code>, CanonicalEvidenceType: <code>{1}</code>, DataEvaluator: <code>{2}</code>, DataOwner: <code>{3}</code>
* RequestTransferEvidenceUSIDT message received - RequestId: <code>{0}</code>
* RequestLookupRoutingInformation message received - CanonicalEvidenceType: <code>{0}</code>, CountryCode: <code>{1}</code>, DataOwnerId: <code>{2}</code>
* Sending request to IDK - URL: <code>{0}</code>
* Looking for Data Owner address - DataOwnerId: <code>{0}</code>

'''Client''' – ''(Info level)''

* Requesting to SMP - ParticipantId: <code>{0}</code>, DocumentTypeId: <code>{1}</code>, MessageType: <code>{2}</code>
* Sending RequestForwardEvidence to the Data Evaluator - RequestId: <code>{0}</code>, DataEvaluatorId: <code>{1}</code>, DataOwnerId: <code>{2}</code>, Endpoint: {3}
* Sending RequestExtractEvidence IM to the Data Owner - RequestId: <code>{0}</code>, CanonicalEvidenceType: <code>{1}</code>, DataEvaluatorId: <code>{2}</code>, DataOwnerId: <code>{3}</code>, Endpoint: <code>{4}</code>
* Sending RequestExtractEvidence USI to the Data Owner - RequestId: <code>{0}</code>, CanonicalEvidenceType: <code>{1}</code>, DataEvaluatorId: <code>{2}</code>, DataOwnerId: <code>{3}</code>, Endpoint: <code>{4}</code>

'''AS4''' – ''(Info level)''

* Sending request message via AS4 gateway - DataEvaluatorId: <code>{0}</code>, DataOwnerId: <code>{1}</code>, CanonicalEvidenceType: <code>{2}</code>
* Sending response message via AS4 gateway - DataEvaluatorId: <code>{0}</code>, Message tag: <code>{1}</code>, CanonicalEvidenceType: <code>{2}</code>
* Processing the request received via AS4 gateway - RequestId: <code>{0}</code>
* Processing the response received via AS4 gateway - RequestId: <code>{0}</code>

'''Errors''' – ''(Error level)''

* The corresponding request to the received response is not found on database - RequestId: <code>{0}</code>
* RequestForwardEvidence has not been sent, unknown Data Evaluator endpoint - RequestId: <code>{0}</code>, DataEvaluatorId: <code>{1}</code>
* RequestTransferEvidence not found on AS4 incoming message
* Error processing incoming message from AS4 gateway
* Error building URI from Data Evaluator endpoint: <code>{0}</code>
* Error sending message to Data Requestor via AS4 gateway - RequestId: <code>{0}</code>
* Data Owner address not found - DataOwnerId: <code>{0}</code>
[1] The <code>{x}</code> symbols are placeholders for dynamic text to be logged.

===Data management===
The Connector stores and manages certain information such as DE endpoints (not to be confused with SMP endpoints), DO endpoints, certain request records for asynchronous response matching, etc. All this data and where to find it is described in the following subsections.

====Data Owner and Data Evaluator addresses====
Once each Data Owner is publishing his Connector service information on the SMP, the request will arrive to that Connector service configured on the SMP (via the AS4 Gateway), and considering that one Connector could be serving to multiples DOs, this Connector has to know the addressing (base endpoint, without path name) information related to a specific participant identifier (e.g. iso6523-actorid-upis::9999:egov) to send forward the request to the corresponding Data Owner, so due to that, the Connector has a configuration file '''de-do.json''' where the information for the data owner and/or the Data Evaluator endpoints is stored. More information is available at [[Connector iteration 2 installation and configuration guide]].
==Security==
The message exchange performed by the Connector has been conceived to ensure different security aspects as:

*'''Authenticity''': ensures the identity of the participant entities and any common component involved in the message exchange. It is achieved through the participant identifiers definition, [[Usage of third party specifications and components|eDelivery]] specification and [[Usage of third party specifications and components|AS4]] implementations.

* '''Integrity''': refers to the accuracy and completeness of data. Security controls focused on integrity are used to prevent data from being modified or misused by an unauthorized party, provided by the WS-security and XML message signature.

*'''Confidentiality''': data confidentiality at message level could be achieved by taking advantage of WS-Security encryption feature in User messages. This message encryption is performed via asymmetric keys: the sender of the message encrypts with the public key of the recipient, so the message can only be decrypted by the recipient, who owns the private key. Those keys should be configured either in the Connector in case of phase4 or in any external AS4 gateway.

===Communications===
The Connector creates a secure context to establish in/outgoing connections with external components.

The main elements for such communication securitisations are:

*'''Private key''': private part of private-public key pair used in the TLS handshake between your server and the connecting clients. This private key must be configured in the Connector properties in order to create the secure context as well in the web server, in the case of reverse proxy or any similar structure. The keys configured on each component are generated under the DE4A management.

*'''Truststore''': used for the storage of certificates from the trusted Certificate Authority (CA), which is used in the verification of the certificate provided by the server in an SSL connection. The Connector provides a default truststore which allows to trust on certificates generated under the main DE4A CA.

====HTTP Proxy mode====
Sometimes, the environments have certain communication structure where the outgoing connections must be performed through an HTTP proxy server. The Connector provides de functionality and proper configuration to perform the communications via an HTTP proxy server.
===Message cryptographic protection ===
The Connector messages exchange can be separated into:

====REST APIs messages====
Once the SSL connection is established, all the data exchanged through it, will be encrypted on transport level based on the SSL context configuration settled, either managed by a reverse proxy on the server environment or configuring the proper application properties.

====AS4 messages====

*'''Phase4''': internally the message is encrypted using a specific keystore configuration only used for this purpose; also the cross-gateways communications are additionally encrypted over the HTTPS secure protocol.

===Message validation===
Message validation is performed at different stages of the Connector data flow, from message structure compliance to content integrity.

====Schema validation====
All the messages produced and consumed by the Connector are performing an XML Schema validation once it is received or sent out. This validation is done by the object conversion library that keeps the schema model including all the structure and content constraints.

====Signature validation====
As well as the XML Schema validation, the Connector performs validations to ensure the content and reliability on certain phases of the message exchange process:

*Services metadata querying
*In the SMP data exchange a message signature validation is being performed to maintain the content reliability. This validation consists of verifying the embedded signature on the message against the trust certificate configured in the Connector for that purpose.
The signature of incoming AS4 messages is verified against the central [[Usage of third party specifications and components|AS4]] Gateway CA globally used in DE4A project, internally validated by the implementation libraries that handle the reception and delivery.

==Technology used==

===System core architecture===
The Connector works as standalone application that runs different web services according to the RESTful API architecture principles. The application is built with the following tools:

*Spring Framework version 5.x.
*Java 11
*Apache HTTP Client 4.x

In addition to the core architecture, the XML Schemas defined to model the exchanged information, data constraints, interfaces, etc. are also important. All this is part of the Connector core through the de4a-commons library, which contains the above-mentioned model as well as utilities and conversion tools.

*Author: ''DE4A (WP5)''
*Repository: https://github.com/de4a-wp5/de4a-commons

===Third party libraries===
As part of the bunch of libraries used by the Connector there are some of the related with the core features and which represent a starting point for the functionalities provided by the Connector.

==== TOOP Connector====
The TOOP Connector is a set of shared utility functions used in the Connector to perform common tasks that are required for a safe and interoperable data exchange. In the initial iteration the latest version of the TOOP Connector technical components were reused mainly for the usage of the built-in phase4 AS4 Gateway. Other elements of the TOOP Connector are currently ignored.

*Author: ''TOOP Project''
*Repository: https://github.com/de4a-wp5/toop-connector-ng

====ph-oton libraries====
Set of Java libraries to build Java web applications.

*Author: ''Philip Helger (phax)''
*Repository: https://github.com/phax/ph-oton

====Peppol commons libraries====
They include the SMP client library used by the Access Points to retrieve service metadata. This library supports the Peppol SMP specification, the OASIS BDXR SMP v1 and OASIS BDXR SMP v2 specification. This project uses Apache HTTP client to perform the REST lookups on foreign SMPs.

*Author: ''Philip Helger (phax)''
*Repository: https://github.com/phax/peppol-commons

=== Data management===
To manage the model and the data stored by the Connector the following technologies are used:

*'''JPA:''' The Java Persistence API is a specification of Java. It is used to persist data between Java object and relational database. JPA acts as a bridge between object-oriented domain models and relational database systems. As JPA is just a specification, it does not perform any operation by itself.

*'''Hibernate:''' An object–relational mapping tool for the Java programming language. It provides a framework for mapping an object-oriented domain model to a relational database. Hibernate handles object–relational impedance mismatch problems by replacing direct, persistent database accesses with high-level object handling functions.

===Utilities libraries===
The project uses several libraries and utilities to process and transform the data. They can be divided according to their nature:

*'''Commercial libraries'''

To perform common and non-business operations on web and data exchange projects, the Connector uses different commercial solutions, also all the libraries embedded in the Java development kit.

*'''In-house solutions'''
The Connector project includes some utilities that allow the data processing and internal tools to perform all the Connector tasks. Those utilities are within the Connector project as a module called ''de4a-commons.''
[[Category:Wip]]

DE4A common specifications and components it2

2022-11-11T15:28:11Z

Javier.ferrero: /* Usage of third-party specifications and components */

This section provides an overview of the common components and specifications required for the evidence exchanges.

== Getting started guide ==
When starting with iteration 2 developments, every partner should follow the [[getting started guide]].

== Checklist for Connectathons ==
A quick guide of points to consider and review prior to the Connectathon sessions has been developed to make the Connectathon sessions more productive. It is available [[DE4A Checklist for Connectathon|here]].
== Common specifications ==
===Usage of third-party specifications and components===
It comprises a list of elements and a description of the third-party libraries and components that have made it possible to build the DE4A components more quickly and allow them to be extended, thus increasing the stability and robustness of the system.

==== eDelivery ====

==== RegRep ====

==== Kafka ====

===[[Common behaviour and interactions between components]]===
Introduction to the chapter, highlighting the fact that the description of the behaviour is done through communication diagrams. Links to the five communication diagrams and the data dictionary.

===[[Summary of software interfaces.|Summary of software interfaces]]===
REST APIs interfaces refer to most of the components involved in the exchange of messages.

===[[DE4A Logs and error messages it2|DE4A Logs and error messages]]===
Definition and reference of error coding and logs handling. It includes standardised log and error messages within the DE4A project to provide a good understanding of the different components regarding their points of failure and the different states in which each system is placed.

== Common Components ==

===[[DE4A Connector it2|DE4A Connector]]===
The main component of the DE4A communication infrastructure for processing request and response messages from DP/DCs. The DE4A connector handles the message exchange process and obtains information from different nodes like IDK or SMP for this purpose. It implements the AS4 Gateway functionality, so it can undertake either Requestor or Transferor roles.

==== [[Installation and configuration guide of the DE4A Connector it2]] ====
Step by step guide to successful configure an instance of the DE4A Connector. Find in this section all aspects related to the different configuration scenarios and keypoints of the system.

=== Issuing Authority Locator ===

=== DE4A SSI Authority Agent ===

=== DE4A SSI Edge Agent ===

== Testing infrastructure ==

=== [[DE4A Playground it2|DE4A Playground]] ===
It comprises a set of components and utilities provided for pilots and partners for testing purposes. In addition it can be used to replace some components that might not yet be available or that they need to be tested in a "real" environment.

=== [[Sample datasets]] ===
This page contains the information for the test cases available in the playground environment.

== DE4A Member States Infrastructure ==
Status of the DE4A Member States infrastructure for the second iteration of the pilots, along with some useful information to bear in mind when setting up such infrastructure.

=== [[Useful information on pilots and participants]] ===
[[Category:Wip]]

DE4A Common Components

2022-11-11T15:27:44Z

Javier.ferrero: /* Third party specifications and components */

This section provides an overview of the common components and specifications required for the evidence exchanges. A high-level conceptual diagram of the envisaged infrastructure, containing the main software components required for the first iteration of the pilots, is presented in the image below.

[[File:DE4A Conceptual Schema.png|alt=DE4A Conceptual Schema|center|thumb|892x892px]]The following table describes the '''common''' components in the above diagram, leaving out those components that are developed or deployed directly by each DE4A participant, namely the Data Evaluator, the Data Owner and the eIDAS Nodes.
{| class="wikitable"
|+
!Component
!Description
|-
|[[DE4A Connector]]
|Technical proxy that allows the final participants to send requests for evidence or responses to other final participants over an eDelivery communication environment
|-
|[[Usage of third party specifications and components|SML]]
|The Service Metadata Locator. Reference instance in the DE4A network
|-
|[[Usage of third party specifications and components|SMP]]
|Service Metadata Publisher
|-
|[[Usage of third party specifications and components|AS4 Gateway]]
|AS4 protocol implementation for the message exchange
|-
|[[Usage of third party specifications and components|Mocked IDK]]
|Testing component for the IAL definition
|-
|[[DE4A SSI Authority Agent|SSI Authority Agent]]
|Enterprise-level solution that enables issuing and submitting diplomas in the form of verifiable credentials/presentations to Issuers/Verifiers.
|-
|[[DE4A SSI Edge Agent|SSI Edge Agent]]
|Mobile digital wallet solution that enables users to manage their digital diplomas and interact with the Issuer's/Verifier's portals.
|}
== Common specifications ==
===[[Usage of third party specifications and components|Third party specifications and components]]===
It comprises a list of elements and a description of the third-party libraries and components that have made it possible to build the DE4A components more quickly and allow them to be extended, thus increasing the stability and robustness of the system.

===[[Description of the software interfaces|Description of common software interfaces]]===
REST APIs interfaces reference for most of the components involved in the message exchanging.

===[[DE4A Logs and error messages]]===
Definition and reference of error coding and logs handling. Includes standardised log and error messages within the DE4A project to provide a good understanding of the different components regarding their points of failure and the different states in which each system is placed.

== Common Components ==

===[[DE4A Connector]]===
The main component of the DE4A communication infrastructure for processing request and response messages from DP/DCs. The DE4A connector handles the message exchange process and obtains information from different nodes like IDK or SMP for this purpose. It implements the AS4 Gateway functionality, so it can undertake either Requestor or Transferor roles.

==== [[DE4A Installation and configuration guide|DE4A Connector installation and configuration guide]] ====
Step by step guide to successful configure an instance of the DE4A Connector. Find in this section all aspects related to the different configuration scenarios and keypoints of the system.

=== [[DE4A SSI Authority Agent]] ===

=== [[DE4A SSI Edge Agent]] ===

== Testing infrastructure ==

=== [[DE4A Playground]] ===
It comprises a set of components and utilities provided for pilots and partners for testing purposes. In addition it can be used to replace some components that might not yet be available or that they need to be tested in a "real" environment.

===[[DE4A Playground joining stages for the first iteration]]===
Besides the Playground as testbed, the final components development and deployments had yet to be accomplished. This sections describes the different stages or milestones set from the pilot perspective while they were gradually increasing their own infrastructures/deployments, and so stepping out from the Playground.
[[Category:Wip]]

== DE4A Member States Infrastructure ==
Status of the DE4A Member States infrastructure for the first iteration of the pilots.
=== [[DE4A Member States Infraestructure|DE4A Member States Infrastructure]] ===

Useful information on pilots and participants

2022-11-05T10:35:37Z

Javier.ferrero: /* Summary of DE4A pilots IT2 */

Useful information about the pilots and the participants in DE4A during the second iteration of the project. This information is intended to serve as a reference for the configuration and operation of the partners' infrastructures and the Playground. Each partner is responsible for entering and keeping the information collected on this Wiki page up-to-date.

== Progress of the deployment of DE4A participants' infrastructures in iteration 2 ==

=== SMP in Member States ===
{| class="wikitable"
!MS
!Member State
!Participant
!Own SMP (Deployed & configured / In progress / No, planned for X)
|-
|'''AT'''
|Austria
|BRZ
|Deployed and configured, phoss 5.7.1, Telesec Certificates
|-
|'''ES'''
| Spain
|SGAD
| Deployed and configured: phoss SMP v5.6.2
|-
|'''LU'''
|Luxembourg
|CTIE
|Not deployed, prevision "before light review"
|-
|'''NL'''
|The Netherlands
|RVO
|Deployed, solving configuration issues
|-
|'''PT'''
| Portugal
|AMA
|Deployed and configured
|-
|'''RO'''
| Romania
|ONRC
|Deployed and configured
|-
|'''RO'''
| Romania
|MoAI
|Not yet deployed
|-
|'''SU'''
|Sweden
|BVE
|Deployed and configured
|-
|'''SI'''
| Slovenia
|SI-MPA
|Deployed and configured to use IAL, configuration verified by Philip
|}

===DE4A Connector in Member States===
{| class="wikitable"
!MS
!Member State
!Participant
!Own Connector (Deployed & configured / In progress / No, planned for X)
|-
|'''AT'''
|Austria
|BRZ
|
|-
|'''ES'''
|Spain
|SGAD
|Deployed & configured: v0.2.6
|-
|'''LU'''
|Luxembourg
|CTIE
|
|-
|'''NL'''
|The Netherlands
|RVO
|Deployed & Configured: v02.6 (Test environment)
|-
|'''PT'''
|Portugal
|AMA
|
|-
|'''RO'''
| Romania
|ONRC
|
|-
|'''RO'''
|Romania
|MoAI
|
|-
|'''SU'''
|Sweden
|BVE
|
|-
|'''SI'''
|Slovenia
|SI-MPA
|Deployed & configured: v0.2.6
|}
== Summary of pilots and participants during the second iteration ==

=== Summary of DE4A pilots IT2 ===
{| class="wikitable"
! colspan="5" |Iteration 2
|-
|'''Pilot'''
|'''Use case'''
|'''Use case name'''
|'''Interaction pattern used'''
|'''Evidence exchanged'''
|-
| rowspan="3" |'''Studying abroad (SA)'''
|UC1.1
|Application to public higher education
|User-Supported Intermediation (USI)
|Higher Education Diploma
Secondary Education Diploma
|-
|UC1.2
|Applying for study grant
|User-Supported Intermediation (USI)
|Higher Education Diploma
Large Family Evidence

Disability Evidence
|-
|UC1.3
|Diploma / Certs / Studies / Professional recognition
|Verifiable Credentials (VC)
|Higher Education Diploma
|-
| rowspan="2" |'''Doing business abroad (DBA)'''
|UC2.1
|Starting a business in another Member State
|Intermediation (IM)
Subscription and Notification (S&N)
|Company Registration
|-
|UC2.2
|Doing business in another Member State
|Intermediation (IM)
Subscription and Notification (S&N)

Lookup (LU)
|Company Registration
"Business events" catalogue
|-
| rowspan="2" |'''Moving abroad (MA)'''
|UC3.1
|Request address change
|Registration: User-Supported Intermediation (USI)
Deregistration: Notification (S&N) and Lookup (LU)
|Domicile Registration Evidence
|-
|UC3.2
|Request an extract or copy of civil state certificate
|User-Supported Intermediation (USI)
|Birth Evidence
Marriage Evidence
|}

=== DE4A pilot participants IT2 ===
{| class="wikitable"
! colspan="4" |Partner
! colspan="3" |SA
! colspan="2" |DBA
! colspan="2" |MA
!
|-
|'''Short name'''
|'''Name'''
|'''Country'''
|'''Participant ID'''
|'''UC1.1'''
|'''UC1.2'''
|'''UC1.3'''
|'''UC2.1'''
|'''UC2.2'''
|'''UC3.1'''
|'''UC3.2'''
|'''Notes'''
|-
|BMDW
|Bundesministerium fuer Digitalisierung und Wirtschaftsstandort
|AT
|iso6523-actorid-upis::9991:at000000271
|
|
|
|DE
DO
|DE

DO
|
|
|
|-
|BRZ
|Bundesrechenzentrum GMBH (Federal Data Center)
|AT
|
|
|
|
|DR
DT
|DR

DT
|
|
|BRZ has no Participant ID, because it is only DR and DT
|-
|SGAD
|Secretaría General de Administración Digital (General Secretariat for Digital Administration)
|ES
|iso6523-actorid-upis::9920:ess2833002e
|DR
DO,DT
|DO,DT
|DP
|
|
|DO,DT
|DE,DR
DO,DT
|Evidence in SA UCs is provided by the DE4A partner UJI.
|-
|UJI
|Universitat Jaume I de Castellón (Jaume I University of Castellón)
|ES
|iso6523-actorid-upis::9920:esq6250003h
|DE*
|
|
|
|
|
|
|*Connector provided by SGAD. UJI is also an evidence provider in all SA UCs through SGAD.
|-
|CTIE
|Centre des Technologies de l'Information de l'Etat (State Information Technology Center)
|LU
|iso6523-actorid-upis::9991:lu000000025
|
|
|
|
|
|DE,DR
DO,DT
|DE,DR
DO,DT
|
|-
|RVO
|Rijksdienst voor Ondernemend Nederland (Netherlands Enterprise Agency)
|NL
|iso6523-actorid-upis::9991:nl000000024-it1
|
|
|
|DE,DR
|DE,DR
|
|
|*9999:nl000000024-test-it1 for test environment
|-
|RVO
|Rijksdienst voor Ondernemend Nederland (Netherlands Enterprise Agency)
|NL
|iso6523-actorid-upis::9991:nl000000106-it1
|
|
|
|DO,DT
|DO,DT
|
|
|*9999:nnl000000106-test-it1 for test environment
|-
|AMA-IP
|Agencia para a Modernizacao Administrativa IP (Administration Modernization Agency)
|PT
|iso6523-actorid-upis::9991:pt000000026
|DR
DO,DT
|DT
|
|
|
|DR
DO,DT
|DR
|AMA-IP consults INESC-ID in some cases when the latter takes the role of DO. Therefore, INESC-ID does not directly take part of the DE4A network as DO, but AMA-IP instead.
|-
|INESC-ID
|Institute for Systems and Computer Engineering, Technology and Science
|PT
|iso6523-actorid-upis::9991:pt990000101
|DE
|
|DC
DP
|
|
|
|
|
|-
|MoAI
|Ministerul Afacerilor Interne (Ministry of Internal Affairs)
|RO
|iso6523-actorid-upis::9991:ro000000005
|
|
|
|
|
|DE,DR

DO,DT
|DE,DR

DO,DT
|
|-
|ORNC
|Oficiul National B22 al Registrului Comertului
|RO
|iso6523-actorid-upis::9991:ro000000006
|
|
|
|DE,DR

DO,DT
|DE,DR

DO,DT
|
|
|
|-
|BVE
|Bolagsverket (Companies Registration Office)
|SE
|iso6523-actorid-upis::9991:se000000013
|
|
|
|DE,DR
|DE,DR
|
|
|
|-
|JSI
|Institut "Jožef Stefan" (Jožef Stefan Institute)
|SI
|iso6523-actorid-upis::9949:si55560822
|
|DE
|
|
|
|
|
|
|-
|MIZŠ
|Ministrstvo za izobraževanje, znanost in šport (Ministry of Education, Science and Sport)
|SI
|iso6523-actorid-upis::9949:si14246821
|DE
DO
|
|DC
DP
|
|
|
|
|*The central preview functionality for DO is provided by SI-MPA.
|-
|SI-MPA
|Ministrstvo za javno upravo (Ministry of Public Administration)
|SI
|iso6523-actorid-upis::9991:si000000015
|DR
DT
|DR
|
|
|
|DR
DT
|DR
DT
|
|-
|MNZ
|Ministrstvo za notranje zadeve (Ministry of the Interior)
|SI
|iso6523-actorid-upis::9949:si52817652
|
|
|
|
|
|DO
|DO
|*The central preview functionality for DO is provided by SI-MPA.
|}

=== Technical information on participants IT2 ===
{| class="wikitable"
!
==== Test domain (Playground) ====
!
==== Pilot domain ====
|-
|
{| class="wikitable"
! colspan="4" |SMP
|-
|'''Country'''
|'''Participant'''
|'''SMP endpoint'''
|'''SMP certificate'''
|-
|ES (shared)
|SGAD
|[https://de4a.redsara.es/sgad-smp https://de4a.redsara.es/sgad-smp/]
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD owncloud folder]
|-
|NL
|RVO
|https://acc-eidas.minez.nl/de4a-smp/
|
|}
|
{| class="wikitable"
! colspan="4" |SMP
|-
|'''Country'''
|'''Participant'''
|'''SMP endpoint'''
|'''SMP certificate'''
|-
|AT
|BRZ
|https://de4a-smp.usp.gv.at/
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD&fileid=1169370 owncloud folder]
|-
|ES
|SGAD
|
|
|-
|LU
|
|
|
|-
|NL
|RVO
|https://acc-eidas.minez.nl/de4a-smp/
|
|-
|PT
|AMA
|[https://pprsmp.iap.gov.pt/ https://pprsmp.iap.gov.pt/smp.iap.gov.pt]
|
|-
|RO
|MOAI
|https://de4a-smp.mai.gov.ro:8443/
|
|-
|SE
|
|
|
|-
|SI
|SI-MPA
|https://toop-smp.pprod.medius.si/public
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SI-MPA owncloud folder]
|}
|-
|
{| class="wikitable"
! colspan="3" |DE
|-
|'''Participant'''
|'''Evidence types consumed'''
|'''DE e-procedure portal'''
|-
|BMDW
|Company Registration
|
|-
|SGAD
|Birth Evidence
Marriage Evidence
|
|-
|UJI
|Higher Education Diploma
|
|-
|CTIE
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|RVO
|Company Registration
|
|-
|INESC-ID
|Higher Education Diploma
Secondary Education Diploma
|
|-
|
|
|
|-
|MoAI
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|ORNC
|Company Registration
|
|-
|BVE
|Company Registration
|
|-
|JSI
|Higher Education Diploma
Large Family Evidence

Disability Evidence
|https://grants.e5.ijs.si/grants/public/
|-
|MIZŠ
|Higher Education Diploma
Secondary Education Diploma
|http://srvas2.rrc.si/prijava/?lang=en
|}
|
{| class="wikitable"
! colspan="3" |DE
|-
|'''Participant'''
|'''Evidence types consumed'''
|'''DE e-procedure portal'''
|-
|BMDW
|Company Registration
|
|-
|SGAD
|Birth Evidence
Marriage Evidence
|
|-
|UJI
|Higher Education Diploma
|
|-
|CTIE
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|RVO
|Company Registration
|https://mijn.rvo.nl/digital-europe-for-all-pilot

(production)
|-
|INESC-ID
|Higher Education Diploma
Secondary Education Diploma
|
|-
|
|
|
|-
|MoAI
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|ORNC
|Company Registration
|
|-
|BVE
|Company Registration
|
|-
|JSI
|Higher Education Diploma
Large Family Evidence

Disability Evidence
|
|-
|MIZŠ
|Higher Education Diploma
Secondary Education Diploma
|
|}
|-
|
{| class="wikitable"
! colspan="3" |DO
|-
|'''Participant'''
|'''Evidence types provided'''
|'''DO evidence portal'''
|-
|BMDW
|Company Registration
|
|-
|SGAD
|Higher Education Diploma
Secondary Education Diploma

Large Family Evidence

Disability Evidence

Domicile Registration Evidence

Birth Evidence

Marriage Evidence

Pension Evidence

Unemployment Evidence

Working Life Evidence
|
|-
|CTIE
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|RVO
|Company Registration
|
|-
|AMA-IP
|Domicile Registration Evidence
|
|-
|INESC-ID
|Higher Education Diploma
|
|-
|MoAI
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|ORNC
|Company Registration
|
|-
|MIZŠ
|Higher Education Diploma
|Direct public access is not enabled
|-
|MNZ
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|Direct public access is not enabled
|}
|
{| class="wikitable"
! colspan="3" |DO
|-
|'''Participant'''
|'''Evidence types provided'''
|'''DO evidence portal'''
|-
|BMDW
|Company Registration
|
|-
|SGAD
|Higher Education Diploma
Secondary Education Diploma

Large Family Evidence

Disability Evidence

Domicile Registration Evidence

Birth Evidence

Marriage Evidence

Pension Evidence

Unemployment Evidence

Working Life Evidence
|
|-
|CTIE
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|RVO
|Company Registration
|
|-
|AMA-IP
|Domicile Registration Evidence
|
|-
|INESC-ID
|Higher Education Diploma
|
|-
|MoAI
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|ORNC
|Company Registration
|
|-
|MIZŠ
|Higher Education Diploma
|Direct public access is not enabled
|-
|MNZ
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|Direct public access is not enabled
|}
|-
|
{| class="wikitable"
! colspan="3" |DR
|-
|'''Participant'''
|'''AS4 certificate'''
|'''Connector endpoint'''
|-
|BRZ
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD&fileid=1169370 owncloud folder]
|https://de4a.usp.gv.at/ado/phase4
|-
|SGAD
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD owncloud folder]
|https://pre-as4gw-dt-de4a.redsara.es/de4a-it2-connector/
|-
|CTIE
|
|
|-
|RVO
|
|[https://acc-eidas.minez.nl/de4a-connector/requestTransferEvidenceIM https://acc-eidas.minez.nl/de4a-connector/]

(iteration 2 version, but DE and DO are still it1 voor IM)
|-
|AMA-IP
|
|http://130.61.108.235/de4a-connector-it2/
|-
|ORNC
|
|
|-
|BVE
|
|
|-
|SI-MPA
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SI-MPA owncloud folder]
|https://toop-as4.pprod.medius.si/
|-
|RO-MOAI
|https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/RO-MOAI&fileid=1173820
|https://de4a.mai.gov.ro:8443/
|}
|
{| class="wikitable"
! colspan="3" |DR
|-
|'''Participant'''
|'''AS4 certificate'''
|'''Connector endpoint'''
|-
|SGAD
|
|
|-
|CTIE
|
|
|-
|RVO
|
|[https://eidas.minez.nl/de4a-connector/requestTransferEvidenceIM https://eidas.minez.nl/de4a-connector/]

(Still Iteration 1 version)
|-
|AMA-IP
|
|http://130.61.108.235/de4a-connector-it2/
|-
|ORNC
|
|
|-
|BVE
|
|
|-
|SI-MPA
|
|
|}
|-
|
{| class="wikitable"
! colspan="3" |DT
|-
|'''Participant'''
|'''AS4 certificate'''
|'''Connector endpoint'''
|-
|BRZ
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD&fileid=1169370 owncloud folder]
|https://de4a.usp.gv.at/ado/phase4
|-
|SGAD
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD owncloud folder]
|https://pre-as4gw-dt-de4a.redsara.es/de4a-it2-connector/
|-
|CTIE
|
|
|-
|RVO
|
|[https://acc-eidas.minez.nl/de4a-connector/requestTransferEvidenceIM https://acc-eidas.minez.nl/de4a-connector/]
|-
|AMA-IP
|
|http://130.61.108.235/de4a-connector-it2/
|-
|MoAI
|
|
|-
|ORNC
|
|
|-
|SI-MPA
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SI-MPA owncloud folder]
|https://toop-as4.pprod.medius.si/
|}
|
{| class="wikitable"
! colspan="3" |DT
|-
|'''Participant'''
|'''AS4 certificate'''
|'''Connector endpoint'''
|-
|BRZ
|
|
|-
|SGAD
|
|
|-
|CTIE
|
|
|-
|RVO
|
|[https://eidas.minez.nl/de4a-connector/requestTransferEvidenceIM https://eidas.minez.nl/de4a-connector/]

(Still Iteration 1 version)
|-
|AMA-IP
|
|http://130.61.108.235/de4a-connector-it2/
|-
|MoAI
|
|
|-
|ORNC
|
|
|-
|SI-MPA
|
|
|}
|}

===DE-DO.json participant endpoint urls===
{| class="wikitable"
!
====Test domain (PRE2b) ====
!
====Pilot domain (PRO2)====
|-
|
{| class="wikitable"
! colspan="5" |Data Owners
|-
|'''Country'''
|'''Participant'''
|'''Participant ID'''
|'''Pattern'''
|'''DO Endpoint URL'''
|-
| rowspan="4" |AT
| rowspan="4" |
| rowspan="4" |iso6523-actorid-upis::99XX:at000000271-test-it2
|IM
|
|-
|USI
|
|-
| LU
|
|-
|SN
|
|-
| rowspan="4" | ES
| rowspan="4" |SGAD
| rowspan="4" |iso6523-actorid-upis::9920:ess2833002e-test-it2
|IM
|https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/requestExtractEvidenceIM
|-
|USI
|https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/do1/usi/extractevidence
|-
|LU
|https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/dataOwner/in/lu/
|-
|SN
|https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/dataOwner/in/sn/
|-
| rowspan="4" |PT
| rowspan="4" |AMA
| rowspan="4" | iso6523-actorid-upis::99XX:pt000000026-test-it2
|IM
|
|-
|USI
|
|-
| LU
|
|-
|SN
|
|-
| rowspan="4" |NL
| rowspan="4" |RVO
| rowspan="4" |iso6523-actorid-upis::9999:nl000000106-test-it1
|IM
|
|-
|USI
|
|-
|LU
|
|-
|SN
|
|-
| rowspan="4" |SI
| rowspan="4" |MIZŠ
| rowspan="4" |iso6523-actorid-upis::9949:si14246821
|IM
|N/A
|-
|USI
|Not publicly disclosed
|-
|LU
|N/A
|-
|SN
|N/A
|-
|SI
|MNZ
|iso6523-actorid-upis::9949:si52817652
|USI
|Not publicly disclosed
|-
| rowspan="4" |SE
| rowspan="4" |BVE
| rowspan="4" |iso6523-actorid-upis::99XX:se000000013-test-it2
|IM
|
|-
|USI
|
|-
|LU
|
|-
|SN
|
|}
{| class="wikitable"
! colspan="5" |Data Evaluators
|-
|'''Country'''
|'''Participant'''
|'''Participant ID'''
|'''Response Type'''
|'''DE Endpoint URL'''
|-
| rowspan="4" | AT
| rowspan="4" |
| rowspan="4" |iso6523-actorid-upis::99XX:at000000271-test-it2
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" |ES
| rowspan="4" |SGAD
| rowspan="4" |iso6523-actorid-upis::9920:ess2833002e-test-it2
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" | ES
| rowspan="4" |UJI
| rowspan="4" |iso6523-actorid-upis::9920:esq6250003h-test-it2
|response
|
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |PT
| rowspan="4" | INESC-ID
| rowspan="4" |iso6523-actorid-upis::9991:pt990000101-test-it2
|response
|
|-
|subscription_resp
| N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |NL
| rowspan="4" |RVO
| rowspan="4" |iso6523-actorid-upis::99XX:nl000000024-test-it1
|response
|N/A
|-
|subscription_resp
| N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |MIZŠ
| rowspan="4" |iso6523-actorid-upis::9949:si14246821
|response
|http://srvas2.rrc.si/de4a/requestForwardEvidence
|-
|subscription_resp
|N/A
|-
|redirect
|http://srvas2.rrc.si/de4a/redirectUser
|-
|notification
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |JSI
| rowspan="4" |iso6523-actorid-upis::9949:si55560822-test-it2
| response
| https://grants.e5.ijs.si/grants/public/de-r/requestForwardEvidence
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |SE
| rowspan="4" |BVE
| rowspan="4" |iso6523-actorid-upis::99XX:se000000013-test-it2
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|}
|
{| class="wikitable"
! colspan="5" |Data Owners
|-
|'''Country'''
|'''Participant'''
|'''Participant ID'''
|'''Pattern'''
|'''DO Endpoint URL'''
|-
| rowspan="4" |AT
| rowspan="4" |
| rowspan="4" |
|IM
|N/A
|-
|USI
|N/A
|-
| LU
|N/A
|-
|SN
|N/A
|-
| rowspan="4" | ES
| rowspan="4" |SGAD
| rowspan="4" |
|IM
|N/A
|-
|USI
|N/A
|-
|LU
|N/A
|-
|SN
|N/A
|-
| rowspan="4" |PT
| rowspan="4" |AMA
| rowspan="4" |
|IM
| N/A
|-
|USI
|N/A
|-
| LU
| N/A
|-
|SN
|N/A
|-
| rowspan="4" |NL
| rowspan="4" |RVO
| rowspan="4" |so6523-actorid-upis::9991:nl000000106-it1
|IM
|N/A
|-
|USI
|N/A
|-
|LU
|N/A
|-
|SN
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |MIZŠ
| rowspan="4" |iso6523-actorid-upis::9949:si14246821
|IM
|N/A
|-
|USI
|Not publicly disclosed
|-
|LU
|N/A
|-
|SN
|N/A
|-
|SI
|MNZ
|iso6523-actorid-upis::9949:si52817652
|USI
|Not publicly disclosed
|-
| rowspan="4" |SE
| rowspan="4" |BVE
| rowspan="4" |
|IM
|N/A
|-
|USI
|N/A
|-
|LU
|N/A
|-
|SN
|N/A
|}
{| class="wikitable"
! colspan="5" |Data Evaluators
|-
|'''Country'''
|'''Participant'''
|'''Participant ID'''
|'''Response Type'''
|'''DE Endpoint URL'''
|-
| rowspan="4" | AT
| rowspan="4" |
| rowspan="4" |
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" |ES
| rowspan="4" |SGAD
| rowspan="4" |
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" | ES
| rowspan="4" |UJI
| rowspan="4" |
|response
|
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |PT
| rowspan="4" | INESC-ID
| rowspan="4" |
|response
|
|-
|subscription_resp
| N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |NL
| rowspan="4" |RVO
| rowspan="4" |iso6523-actorid-upis::9991:nl000000024-it1
|response
|N/A
|-
|subscription_resp
| N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |MIZŠ
| rowspan="4" |iso6523-actorid-upis::9949:si14246821
|response
|
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |JSI
| rowspan="4" |iso6523-actorid-upis::9949:si55560822
| response
|
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |SE
| rowspan="4" |BVE
| rowspan="4" |
|response
| N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|}

|}

==DE4A infrastructure IT2==
===Playground infrastructure IT2===
The following diagram depicts the Playground infrastructure for the second iteration, with the deployment of its corresponding components.[[File:DE4A network IT2-Playground IT2.drawio.png|frame|alt=|none]]

===Pilot partners infrastructure flavours IT2 ===
The following two diagrams outline the general infrastructure expected from the Member States and partners involved in the pilots. Each Connector is in turn connected and exchanges data with the corresponding Connector (DR or DT) of the Playground or other partners.

At this stage, all DE4A participants are expected to follow the set-up A, while only Romania is expected to follow set-up B.[[File:DE4A network IT2-Country set-up A.drawio.png|frame|alt=|left]]

[[File:DE4A network IT2-Country set-up B.drawio.png|frame|alt=|none]]

== Domains and types of participant IDs ==

===DE4A domains===
In DE4A, there are two types of participants:

*Imaginary participants: intended to query the examples stored in the Mocked DO.
*Real participants: intended to retrieve data directly returned by partners.

At the same time, for the real participants, there are also two “domains”:

*Test domain: only fake data is used for test purposes. It is the domain related to the DE4A Playground, where participants return datasets from test sources.
*Pilot domain: real data from real citizens and companies is supposed to be used. It is the environment used for the running phase of the pilots, where participants access to their real registries and return real evidence from them.

Finally, the project is divided into two iterations where each of them needs a copy of those two domains, and where some overlap between them occurs.
[[File:Domain overlap.png|none|thumb|910x910px]]
As the DE4A project uses the dynamic discovery of eDelivery, where there cannot be duplicate participant IDs targeting to different Connectors (depending on the domain concerned), we need to define a different participant ID schema per each domain:

*'''PRE1a''': Imaginary participants stored in the Mocked DO for iteration 1 for testing. The related evidence is stored in the Mocked DO deployed in SGAD (ES).
** Scheme identifier used: “'''9999'''”.
** Suffix used: “'''-it1'''”.
**E.g. iso6523-actorid-upis::99'''99''':ess2833002e'''-it1'''

*'''PRE1b:''' Simulated data returned by the real participants used for testing in Playground iteration 1. The related evidence is located in each partner’s infrastructure, within their test domain.
**Scheme identifier used: “'''99XX'''”, where “XX” depends on the identifier each participant is using.
**Suffix used: “'''-it1'''”.
**E.g. iso6523-actorid-upis::99'''20''':ess2833002e'''-it1'''
*'''PRO1:''' Real data returned by the real participants during the execution of phase 1 of the pilot. The related evidence is located in each partner’s infrastructure, within their pilot domain.
**Scheme identifier used: “'''99XX'''”, where “XX” depends on the identifier each participant is using. It is the “real” participant ID.
**Suffix used: ''none'', since there is no overlap between phases 1 and 2 of the pilots.
**E.g. iso6523-actorid-upis::99'''20''':ess2833002e
*'''PRE2a:''' Imaginary participants stored in the Mocked DO for iteration 2 for testing. The related evidence is stored in the Mocked DO deployed in SGAD (ES).
**Scheme identifier used: “'''9999'''”.
**Suffix used: “'''-mock-it2'''”.
**E.g. iso6523-actorid-upis::99'''99''':ess2833002e'''-mock-it2'''
*'''PRE2b:''' Simulated data returned by the real participants used for testing in Playground iteration 2. The related evidence is located in each partner’s infrastructure, within their test domain.
**Scheme identifier used: “'''99XX'''”, where “XX” depends on the identifier each participant is using.
**Suffix used: “'''-test-it2'''”.
**E.g. iso6523-actorid-upis::99'''20''':ess2833002e'''-test-it2'''
*'''PRO2:''' Real data returned by the real participants during the execution of phase 2 of the pilot. The related evidence is located in each partner’s infrastructure, within their pilot domain.
**Scheme identifier used: “'''99XX'''”, where “XX” depends on the identifier each participant is using. It is the “real” participant ID.
**Suffix used: ''none'', since there is no overlap between phases 1 and 2 of the pilots.
**E.g. iso6523-actorid-upis::99'''20''':ess2833002e

Therefore, DE4A domains are differentiated by the participant ID schema used.

===Location of the participant IDs===
These different participant IDs must be stored in their corresponding IDKs and SMPs and configured to return the proper information:

*'''PRE1a:''' Imaginary participants
**IDK: none (for these participants, the mocked DE knows which the imaginary participants are and which DO to query, namely, the mocked DO of the first iteration).
**SMP: shared SMP of the Playground IT1. It returns the routing information of the targeted Connector (DR/DT) of the Playground IT1.
*'''PRE1b''': Simulated data from real participants
**IDK: mocked IDK of the Playground IT1.
**SMP: shared SMP of the Playground IT1. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.
*'''PRO1:''' Real data from real participants
**IDK: mocked IDK of the pilot running environment.
**SMP: national SMP of the requested participant. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.
***For the first pilot running phase, partners who have not yet deployed their own SMPs will be able to use a shared SMP provided by one of the partners with an available SMP. In such cases, the routing information of those partners will be stored in this shared SMP.
*'''PRE2a:''' Imaginary participants
**IDK: Central IAL. Its information is automatically updated and fed from the SMPs connected to it.
**SMP: shared SMP of the Playground IT2. It returns the routing information of the targeted Connector (DR/DT) of the Playground IT2.
*'''PRE2b:''' Simulated data from real participants
**IDK: Central IAL. Its information is automatically updated and fed from the SMPs connected to it.
**SMP: national SMP of the requested participant. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.
*'''PRO2:''' Real data from real participants
**IDK: Central IAL. Its information is automatically updated and fed from the SMPs connected to it.
**SMP: national SMP of the requested participant. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.

Useful information on pilots and participants

2022-11-01T15:33:01Z

Javier.ferrero: Minor fixes

Useful information about the pilots and the participants in DE4A during the second iteration of the project. This information is intended to serve as a reference for the configuration and operation of the partners' infrastructures and the Playground. Each partner is responsible for entering and keeping the information collected on this Wiki page up-to-date.

== Progress of the deployment of DE4A participants' infrastructures in iteration 2 ==

=== SMP in Member States ===
{| class="wikitable"
!MS
!Member State
!Participant
!Own SMP (Deployed & configured / In progress / No, planned for X)
|-
|'''AT'''
|Austria
|BRZ
|Deployed and configured, phoss 5.7.1, Telesec Certificates
|-
|'''ES'''
| Spain
|SGAD
| Deployed and configured: phoss SMP v5.6.2
|-
|'''LU'''
|Luxembourg
|CTIE
|Not deployed, prevision "before light review"
|-
|'''NL'''
|The Netherlands
|RVO
|Deployed, solving configuration issues
|-
|'''PT'''
| Portugal
|AMA
|Deployed and configured
|-
|'''RO'''
| Romania
|ONRC
|Deployed and configured
|-
|'''RO'''
| Romania
|MoAI
|Not yet deployed
|-
|'''SU'''
|Sweden
|BVE
|Deployed and configured
|-
|'''SI'''
| Slovenia
|SI-MPA
|Deployed and configured to use IAL, configuration verified by Philip
|}

===DE4A Connector in Member States===
{| class="wikitable"
!MS
!Member State
!Participant
!Own Connector (Deployed & configured / In progress / No, planned for X)
|-
|'''AT'''
|Austria
|BRZ
|
|-
|'''ES'''
|Spain
|SGAD
|Deployed & configured: v0.2.6
|-
|'''LU'''
|Luxembourg
|CTIE
|
|-
|'''NL'''
|The Netherlands
|RVO
|Deployed & Configured: v02.6 (Test environment)
|-
|'''PT'''
|Portugal
|AMA
|
|-
|'''RO'''
| Romania
|ONRC
|
|-
|'''RO'''
|Romania
|MoAI
|
|-
|'''SU'''
|Sweden
|BVE
|
|-
|'''SI'''
|Slovenia
|SI-MPA
|Deployed & configured: v0.2.6
|}
== Summary of pilots and participants during the second iteration ==

=== Summary of DE4A pilots IT2 ===
{| class="wikitable"
! colspan="5" |Iteration 2
|-
|'''Pilot'''
|'''Use case'''
|'''Use case name'''
|'''Interaction pattern used'''
|'''Evidence exchanged'''
|-
| rowspan="3" |'''Studying abroad (SA)'''
|UC1.1
|Application to public higher education
|User-Supported Intermediation (USI)
|Higher Education Diploma
Secondary Education Diploma
|-
|UC1.2
|Applying for study grant
|User-Supported Intermediation (USI)
|Higher Education Diploma
Large Family Evidence

Disability Evidence
|-
|UC1.3
|Diploma / Certs / Studies / Professional recognition
|Verifiable Credentials (VC)
|Higher Education Diploma
|-
| rowspan="2" |'''Doing business abroad (DBA)'''
|UC2.1
|Starting a business in another Member State
|Intermediation (IM)
Subscription and Notification (S&N)
|Company Registration
|-
|UC2.2
|Doing business in another Member State
|Intermediation (IM)
Subscription and Notification (S&N)

Lookup (LU)
|Company Registration
|-
| rowspan="2" |'''Moving abroad (MA)'''
|UC3.1
|Request address change
|Registration: User-Supported Intermediation (USI)
Deregistration: Notification (S&N) and Lookup (LU)
|Domicile Registration Evidence
|-
|UC3.2
|Request an extract or copy of civil state certificate
|User-Supported Intermediation (USI)
|Birth Evidence
Marriage Evidence
|}

=== DE4A pilot participants IT2 ===
{| class="wikitable"
! colspan="4" |Partner
! colspan="3" |SA
! colspan="2" |DBA
! colspan="2" |MA
!
|-
|'''Short name'''
|'''Name'''
|'''Country'''
|'''Participant ID'''
|'''UC1.1'''
|'''UC1.2'''
|'''UC1.3'''
|'''UC2.1'''
|'''UC2.2'''
|'''UC3.1'''
|'''UC3.2'''
|'''Notes'''
|-
|BMDW
|Bundesministerium fuer Digitalisierung und Wirtschaftsstandort
|AT
|iso6523-actorid-upis::9991:at000000271
|
|
|
|DE
DO
|DE

DO
|
|
|
|-
|BRZ
|Bundesrechenzentrum GMBH (Federal Data Center)
|AT
|
|
|
|
|DR
DT
|DR

DT
|
|
|BRZ has no Participant ID, because it is only DR and DT
|-
|SGAD
|Secretaría General de Administración Digital (General Secretariat for Digital Administration)
|ES
|iso6523-actorid-upis::9920:ess2833002e
|DR
DO,DT
|DO,DT
|DP
|
|
|DO,DT
|DE,DR
DO,DT
|Evidence in SA UCs is provided by the DE4A partner UJI.
|-
|UJI
|Universitat Jaume I de Castellón (Jaume I University of Castellón)
|ES
|iso6523-actorid-upis::9920:esq6250003h
|DE*
|
|
|
|
|
|
|*Connector provided by SGAD. UJI is also an evidence provider in all SA UCs through SGAD.
|-
|CTIE
|Centre des Technologies de l'Information de l'Etat (State Information Technology Center)
|LU
|iso6523-actorid-upis::9991:lu000000025
|
|
|
|
|
|DE,DR
DO,DT
|DE,DR
DO,DT
|
|-
|RVO
|Rijksdienst voor Ondernemend Nederland (Netherlands Enterprise Agency)
|NL
|iso6523-actorid-upis::9991:nl000000024-it1
|
|
|
|DE,DR
|DE,DR
|
|
|*9999:nl000000024-test-it1 for test environment
|-
|RVO
|Rijksdienst voor Ondernemend Nederland (Netherlands Enterprise Agency)
|NL
|iso6523-actorid-upis::9991:nl000000106-it1
|
|
|
|DO,DT
|DO,DT
|
|
|*9999:nnl000000106-test-it1 for test environment
|-
|AMA-IP
|Agencia para a Modernizacao Administrativa IP (Administration Modernization Agency)
|PT
|iso6523-actorid-upis::9991:pt000000026
|DR
DO,DT
|DT
|
|
|
|DR
DO,DT
|DR
|AMA-IP consults INESC-ID in some cases when the latter takes the role of DO. Therefore, INESC-ID does not directly take part of the DE4A network as DO, but AMA-IP instead.
|-
|INESC-ID
|Institute for Systems and Computer Engineering, Technology and Science
|PT
|iso6523-actorid-upis::9991:pt990000101
|DE
|
|DC
DP
|
|
|
|
|
|-
|MoAI
|Ministerul Afacerilor Interne (Ministry of Internal Affairs)
|RO
|iso6523-actorid-upis::9991:ro000000005
|
|
|
|
|
|DE,DR

DO,DT
|DE,DR

DO,DT
|
|-
|ORNC
|Oficiul National B22 al Registrului Comertului
|RO
|iso6523-actorid-upis::9991:ro000000006
|
|
|
|DE,DR

DO,DT
|DE,DR

DO,DT
|
|
|
|-
|BVE
|Bolagsverket (Companies Registration Office)
|SE
|iso6523-actorid-upis::9991:se000000013
|
|
|
|DE,DR
|DE,DR
|
|
|
|-
|JSI
|Institut "Jožef Stefan" (Jožef Stefan Institute)
|SI
|iso6523-actorid-upis::9949:si55560822
|
|DE
|
|
|
|
|
|
|-
|MIZŠ
|Ministrstvo za izobraževanje, znanost in šport (Ministry of Education, Science and Sport)
|SI
|iso6523-actorid-upis::9949:si14246821
|DE
DO
|
|DC
DP
|
|
|
|
|*The central preview functionality for DO is provided by SI-MPA.
|-
|SI-MPA
|Ministrstvo za javno upravo (Ministry of Public Administration)
|SI
|iso6523-actorid-upis::9991:si000000015
|DR
DT
|DR
|
|
|
|DR
DT
|DR
DT
|
|-
|MNZ
|Ministrstvo za notranje zadeve (Ministry of the Interior)
|SI
|iso6523-actorid-upis::9949:si52817652
|
|
|
|
|
|DO
|DO
|*The central preview functionality for DO is provided by SI-MPA.
|}

=== Technical information on participants IT2 ===
{| class="wikitable"
!
==== Test domain (Playground) ====
!
==== Pilot domain ====
|-
|
{| class="wikitable"
! colspan="4" |SMP
|-
|'''Country'''
|'''Participant'''
|'''SMP endpoint'''
|'''SMP certificate'''
|-
|ES (shared)
|SGAD
|[https://de4a.redsara.es/sgad-smp https://de4a.redsara.es/sgad-smp/]
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD owncloud folder]
|-
|NL
|RVO
|https://acc-eidas.minez.nl/de4a-smp/
|
|}
|
{| class="wikitable"
! colspan="4" |SMP
|-
|'''Country'''
|'''Participant'''
|'''SMP endpoint'''
|'''SMP certificate'''
|-
|AT
|BRZ
|https://de4a-smp.usp.gv.at/
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD&fileid=1169370 owncloud folder]
|-
|ES
|SGAD
|
|
|-
|LU
|
|
|
|-
|NL
|RVO
|https://acc-eidas.minez.nl/de4a-smp/
|
|-
|PT
|AMA
|[https://pprsmp.iap.gov.pt/ https://pprsmp.iap.gov.pt/smp.iap.gov.pt]
|
|-
|RO
|MOAI
|https://de4a-smp.mai.gov.ro:8443/
|
|-
|SE
|
|
|
|-
|SI
|SI-MPA
|https://toop-smp.pprod.medius.si/public
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SI-MPA owncloud folder]
|}
|-
|
{| class="wikitable"
! colspan="3" |DE
|-
|'''Participant'''
|'''Evidence types consumed'''
|'''DE e-procedure portal'''
|-
|BMDW
|Company Registration
|
|-
|SGAD
|Birth Evidence
Marriage Evidence
|
|-
|UJI
|Higher Education Diploma
|
|-
|CTIE
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|RVO
|Company Registration
|
|-
|INESC-ID
|Higher Education Diploma
Secondary Education Diploma
|
|-
|
|
|
|-
|MoAI
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|ORNC
|Company Registration
|
|-
|BVE
|Company Registration
|
|-
|JSI
|Higher Education Diploma
Large Family Evidence

Disability Evidence
|https://grants.e5.ijs.si/grants/public/
|-
|MIZŠ
|Higher Education Diploma
Secondary Education Diploma
|http://srvas2.rrc.si/prijava/?lang=en
|}
|
{| class="wikitable"
! colspan="3" |DE
|-
|'''Participant'''
|'''Evidence types consumed'''
|'''DE e-procedure portal'''
|-
|BMDW
|Company Registration
|
|-
|SGAD
|Birth Evidence
Marriage Evidence
|
|-
|UJI
|Higher Education Diploma
|
|-
|CTIE
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|RVO
|Company Registration
|https://mijn.rvo.nl/digital-europe-for-all-pilot

(production)
|-
|INESC-ID
|Higher Education Diploma
Secondary Education Diploma
|
|-
|
|
|
|-
|MoAI
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|ORNC
|Company Registration
|
|-
|BVE
|Company Registration
|
|-
|JSI
|Higher Education Diploma
Large Family Evidence

Disability Evidence
|
|-
|MIZŠ
|Higher Education Diploma
Secondary Education Diploma
|
|}
|-
|
{| class="wikitable"
! colspan="3" |DO
|-
|'''Participant'''
|'''Evidence types provided'''
|'''DO evidence portal'''
|-
|BMDW
|Company Registration
|
|-
|SGAD
|Higher Education Diploma
Secondary Education Diploma

Large Family Evidence

Disability Evidence

Domicile Registration Evidence

Birth Evidence

Marriage Evidence

Pension Evidence

Unemployment Evidence

Working Life Evidence
|
|-
|CTIE
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|RVO
|Company Registration
|
|-
|AMA-IP
|Domicile Registration Evidence
|
|-
|INESC-ID
|Higher Education Diploma
|
|-
|MoAI
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|ORNC
|Company Registration
|
|-
|MIZŠ
|Higher Education Diploma
|Direct public access is not enabled
|-
|MNZ
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|Direct public access is not enabled
|}
|
{| class="wikitable"
! colspan="3" |DO
|-
|'''Participant'''
|'''Evidence types provided'''
|'''DO evidence portal'''
|-
|BMDW
|Company Registration
|
|-
|SGAD
|Higher Education Diploma
Secondary Education Diploma

Large Family Evidence

Disability Evidence

Domicile Registration Evidence

Birth Evidence

Marriage Evidence

Pension Evidence

Unemployment Evidence

Working Life Evidence
|
|-
|CTIE
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|RVO
|Company Registration
|
|-
|AMA-IP
|Domicile Registration Evidence
|
|-
|INESC-ID
|Higher Education Diploma
|
|-
|MoAI
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|ORNC
|Company Registration
|
|-
|MIZŠ
|Higher Education Diploma
|Direct public access is not enabled
|-
|MNZ
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|Direct public access is not enabled
|}
|-
|
{| class="wikitable"
! colspan="3" |DR
|-
|'''Participant'''
|'''AS4 certificate'''
|'''Connector endpoint'''
|-
|BRZ
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD&fileid=1169370 owncloud folder]
|https://de4a.usp.gv.at/ado/phase4
|-
|SGAD
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD owncloud folder]
|https://pre-as4gw-dt-de4a.redsara.es/de4a-it2-connector/
|-
|CTIE
|
|
|-
|RVO
|
|[https://acc-eidas.minez.nl/de4a-connector/requestTransferEvidenceIM https://acc-eidas.minez.nl/de4a-connector/]

(iteration 2 version, but DE and DO are still it1 voor IM)
|-
|AMA-IP
|
|http://130.61.108.235/de4a-connector-it2/
|-
|ORNC
|
|
|-
|BVE
|
|
|-
|SI-MPA
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SI-MPA owncloud folder]
|https://toop-as4.pprod.medius.si/
|-
|RO-MOAI
|https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/RO-MOAI&fileid=1173820
|https://de4a.mai.gov.ro:8443/
|}
|
{| class="wikitable"
! colspan="3" |DR
|-
|'''Participant'''
|'''AS4 certificate'''
|'''Connector endpoint'''
|-
|SGAD
|
|
|-
|CTIE
|
|
|-
|RVO
|
|[https://eidas.minez.nl/de4a-connector/requestTransferEvidenceIM https://eidas.minez.nl/de4a-connector/]

(Still Iteration 1 version)
|-
|AMA-IP
|
|http://130.61.108.235/de4a-connector-it2/
|-
|ORNC
|
|
|-
|BVE
|
|
|-
|SI-MPA
|
|
|}
|-
|
{| class="wikitable"
! colspan="3" |DT
|-
|'''Participant'''
|'''AS4 certificate'''
|'''Connector endpoint'''
|-
|BRZ
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD&fileid=1169370 owncloud folder]
|https://de4a.usp.gv.at/ado/phase4
|-
|SGAD
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD owncloud folder]
|https://pre-as4gw-dt-de4a.redsara.es/de4a-it2-connector/
|-
|CTIE
|
|
|-
|RVO
|
|[https://acc-eidas.minez.nl/de4a-connector/requestTransferEvidenceIM https://acc-eidas.minez.nl/de4a-connector/]
|-
|AMA-IP
|
|http://130.61.108.235/de4a-connector-it2/
|-
|MoAI
|
|
|-
|ORNC
|
|
|-
|SI-MPA
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SI-MPA owncloud folder]
|https://toop-as4.pprod.medius.si/
|}
|
{| class="wikitable"
! colspan="3" |DT
|-
|'''Participant'''
|'''AS4 certificate'''
|'''Connector endpoint'''
|-
|BRZ
|
|
|-
|SGAD
|
|
|-
|CTIE
|
|
|-
|RVO
|
|[https://eidas.minez.nl/de4a-connector/requestTransferEvidenceIM https://eidas.minez.nl/de4a-connector/]

(Still Iteration 1 version)
|-
|AMA-IP
|
|http://130.61.108.235/de4a-connector-it2/
|-
|MoAI
|
|
|-
|ORNC
|
|
|-
|SI-MPA
|
|
|}
|}

===DE-DO.json participant endpoint urls===
{| class="wikitable"
!
====Test domain (PRE2b) ====
!
====Pilot domain (PRO2)====
|-
|
{| class="wikitable"
! colspan="5" |Data Owners
|-
|'''Country'''
|'''Participant'''
|'''Participant ID'''
|'''Pattern'''
|'''DO Endpoint URL'''
|-
| rowspan="4" |AT
| rowspan="4" |
| rowspan="4" |iso6523-actorid-upis::99XX:at000000271-test-it2
|IM
|
|-
|USI
|
|-
| LU
|
|-
|SN
|
|-
| rowspan="4" | ES
| rowspan="4" |SGAD
| rowspan="4" |iso6523-actorid-upis::9920:ess2833002e-test-it2
|IM
|https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/requestExtractEvidenceIM
|-
|USI
|https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/do1/usi/extractevidence
|-
|LU
|https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/dataOwner/in/lu/
|-
|SN
|https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/dataOwner/in/sn/
|-
| rowspan="4" |PT
| rowspan="4" |AMA
| rowspan="4" | iso6523-actorid-upis::99XX:pt000000026-test-it2
|IM
|
|-
|USI
|
|-
| LU
|
|-
|SN
|
|-
| rowspan="4" |NL
| rowspan="4" |RVO
| rowspan="4" |iso6523-actorid-upis::9999:nl000000106-test-it1
|IM
|
|-
|USI
|
|-
|LU
|
|-
|SN
|
|-
| rowspan="4" |SI
| rowspan="4" |MIZŠ
| rowspan="4" |iso6523-actorid-upis::9949:si14246821
|IM
|N/A
|-
|USI
|Not publicly disclosed
|-
|LU
|N/A
|-
|SN
|N/A
|-
|SI
|MNZ
|iso6523-actorid-upis::9949:si52817652
|USI
|Not publicly disclosed
|-
| rowspan="4" |SE
| rowspan="4" |BVE
| rowspan="4" |iso6523-actorid-upis::99XX:se000000013-test-it2
|IM
|
|-
|USI
|
|-
|LU
|
|-
|SN
|
|}
{| class="wikitable"
! colspan="5" |Data Evaluators
|-
|'''Country'''
|'''Participant'''
|'''Participant ID'''
|'''Response Type'''
|'''DE Endpoint URL'''
|-
| rowspan="4" | AT
| rowspan="4" |
| rowspan="4" |iso6523-actorid-upis::99XX:at000000271-test-it2
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" |ES
| rowspan="4" |SGAD
| rowspan="4" |iso6523-actorid-upis::9920:ess2833002e-test-it2
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" | ES
| rowspan="4" |UJI
| rowspan="4" |iso6523-actorid-upis::9920:esq6250003h-test-it2
|response
|
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |PT
| rowspan="4" | INESC-ID
| rowspan="4" |iso6523-actorid-upis::9991:pt990000101-test-it2
|response
|
|-
|subscription_resp
| N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |NL
| rowspan="4" |RVO
| rowspan="4" |iso6523-actorid-upis::99XX:nl000000024-test-it1
|response
|N/A
|-
|subscription_resp
| N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |MIZŠ
| rowspan="4" |iso6523-actorid-upis::9949:si14246821
|response
|http://srvas2.rrc.si/de4a/requestForwardEvidence
|-
|subscription_resp
|N/A
|-
|redirect
|http://srvas2.rrc.si/de4a/redirectUser
|-
|notification
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |JSI
| rowspan="4" |iso6523-actorid-upis::9949:si55560822-test-it2
| response
| https://grants.e5.ijs.si/grants/public/de-r/requestForwardEvidence
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |SE
| rowspan="4" |BVE
| rowspan="4" |iso6523-actorid-upis::99XX:se000000013-test-it2
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|}
|
{| class="wikitable"
! colspan="5" |Data Owners
|-
|'''Country'''
|'''Participant'''
|'''Participant ID'''
|'''Pattern'''
|'''DO Endpoint URL'''
|-
| rowspan="4" |AT
| rowspan="4" |
| rowspan="4" |
|IM
|N/A
|-
|USI
|N/A
|-
| LU
|N/A
|-
|SN
|N/A
|-
| rowspan="4" | ES
| rowspan="4" |SGAD
| rowspan="4" |
|IM
|N/A
|-
|USI
|N/A
|-
|LU
|N/A
|-
|SN
|N/A
|-
| rowspan="4" |PT
| rowspan="4" |AMA
| rowspan="4" |
|IM
| N/A
|-
|USI
|N/A
|-
| LU
| N/A
|-
|SN
|N/A
|-
| rowspan="4" |NL
| rowspan="4" |RVO
| rowspan="4" |so6523-actorid-upis::9991:nl000000106-it1
|IM
|N/A
|-
|USI
|N/A
|-
|LU
|N/A
|-
|SN
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |MIZŠ
| rowspan="4" |iso6523-actorid-upis::9949:si14246821
|IM
|N/A
|-
|USI
|Not publicly disclosed
|-
|LU
|N/A
|-
|SN
|N/A
|-
|SI
|MNZ
|iso6523-actorid-upis::9949:si52817652
|USI
|Not publicly disclosed
|-
| rowspan="4" |SE
| rowspan="4" |BVE
| rowspan="4" |
|IM
|N/A
|-
|USI
|N/A
|-
|LU
|N/A
|-
|SN
|N/A
|}
{| class="wikitable"
! colspan="5" |Data Evaluators
|-
|'''Country'''
|'''Participant'''
|'''Participant ID'''
|'''Response Type'''
|'''DE Endpoint URL'''
|-
| rowspan="4" | AT
| rowspan="4" |
| rowspan="4" |
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" |ES
| rowspan="4" |SGAD
| rowspan="4" |
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" | ES
| rowspan="4" |UJI
| rowspan="4" |
|response
|
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |PT
| rowspan="4" | INESC-ID
| rowspan="4" |
|response
|
|-
|subscription_resp
| N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |NL
| rowspan="4" |RVO
| rowspan="4" |iso6523-actorid-upis::9991:nl000000024-it1
|response
|N/A
|-
|subscription_resp
| N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |MIZŠ
| rowspan="4" |iso6523-actorid-upis::9949:si14246821
|response
|
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |JSI
| rowspan="4" |iso6523-actorid-upis::9949:si55560822
| response
|
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |SE
| rowspan="4" |BVE
| rowspan="4" |
|response
| N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|}

|}

==DE4A infrastructure IT2==
===Playground infrastructure IT2===
The following diagram depicts the Playground infrastructure for the second iteration, with the deployment of its corresponding components.[[File:DE4A network IT2-Playground IT2.drawio.png|frame|alt=|none]]

===Pilot partners infrastructure flavours IT2 ===
The following two diagrams outline the general infrastructure expected from the Member States and partners involved in the pilots. Each Connector is in turn connected and exchanges data with the corresponding Connector (DR or DT) of the Playground or other partners.

At this stage, all DE4A participants are expected to follow the set-up A, while only Romania is expected to follow set-up B.[[File:DE4A network IT2-Country set-up A.drawio.png|frame|alt=|left]]

[[File:DE4A network IT2-Country set-up B.drawio.png|frame|alt=|none]]

== Domains and types of participant IDs ==

===DE4A domains===
In DE4A, there are two types of participants:

*Imaginary participants: intended to query the examples stored in the Mocked DO.
*Real participants: intended to retrieve data directly returned by partners.

At the same time, for the real participants, there are also two “domains”:

*Test domain: only fake data is used for test purposes. It is the domain related to the DE4A Playground, where participants return datasets from test sources.
*Pilot domain: real data from real citizens and companies is supposed to be used. It is the environment used for the running phase of the pilots, where participants access to their real registries and return real evidence from them.

Finally, the project is divided into two iterations where each of them needs a copy of those two domains, and where some overlap between them occurs.
[[File:Domain overlap.png|none|thumb|910x910px]]
As the DE4A project uses the dynamic discovery of eDelivery, where there cannot be duplicate participant IDs targeting to different Connectors (depending on the domain concerned), we need to define a different participant ID schema per each domain:

*'''PRE1a''': Imaginary participants stored in the Mocked DO for iteration 1 for testing. The related evidence is stored in the Mocked DO deployed in SGAD (ES).
** Scheme identifier used: “'''9999'''”.
** Suffix used: “'''-it1'''”.
**E.g. iso6523-actorid-upis::99'''99''':ess2833002e'''-it1'''

*'''PRE1b:''' Simulated data returned by the real participants used for testing in Playground iteration 1. The related evidence is located in each partner’s infrastructure, within their test domain.
**Scheme identifier used: “'''99XX'''”, where “XX” depends on the identifier each participant is using.
**Suffix used: “'''-it1'''”.
**E.g. iso6523-actorid-upis::99'''20''':ess2833002e'''-it1'''
*'''PRO1:''' Real data returned by the real participants during the execution of phase 1 of the pilot. The related evidence is located in each partner’s infrastructure, within their pilot domain.
**Scheme identifier used: “'''99XX'''”, where “XX” depends on the identifier each participant is using. It is the “real” participant ID.
**Suffix used: ''none'', since there is no overlap between phases 1 and 2 of the pilots.
**E.g. iso6523-actorid-upis::99'''20''':ess2833002e
*'''PRE2a:''' Imaginary participants stored in the Mocked DO for iteration 2 for testing. The related evidence is stored in the Mocked DO deployed in SGAD (ES).
**Scheme identifier used: “'''9999'''”.
**Suffix used: “'''-mock-it2'''”.
**E.g. iso6523-actorid-upis::99'''99''':ess2833002e'''-mock-it2'''
*'''PRE2b:''' Simulated data returned by the real participants used for testing in Playground iteration 2. The related evidence is located in each partner’s infrastructure, within their test domain.
**Scheme identifier used: “'''99XX'''”, where “XX” depends on the identifier each participant is using.
**Suffix used: “'''-test-it2'''”.
**E.g. iso6523-actorid-upis::99'''20''':ess2833002e'''-test-it2'''
*'''PRO2:''' Real data returned by the real participants during the execution of phase 2 of the pilot. The related evidence is located in each partner’s infrastructure, within their pilot domain.
**Scheme identifier used: “'''99XX'''”, where “XX” depends on the identifier each participant is using. It is the “real” participant ID.
**Suffix used: ''none'', since there is no overlap between phases 1 and 2 of the pilots.
**E.g. iso6523-actorid-upis::99'''20''':ess2833002e

Therefore, DE4A domains are differentiated by the participant ID schema used.

===Location of the participant IDs===
These different participant IDs must be stored in their corresponding IDKs and SMPs and configured to return the proper information:

*'''PRE1a:''' Imaginary participants
**IDK: none (for these participants, the mocked DE knows which the imaginary participants are and which DO to query, namely, the mocked DO of the first iteration).
**SMP: shared SMP of the Playground IT1. It returns the routing information of the targeted Connector (DR/DT) of the Playground IT1.
*'''PRE1b''': Simulated data from real participants
**IDK: mocked IDK of the Playground IT1.
**SMP: shared SMP of the Playground IT1. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.
*'''PRO1:''' Real data from real participants
**IDK: mocked IDK of the pilot running environment.
**SMP: national SMP of the requested participant. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.
***For the first pilot running phase, partners who have not yet deployed their own SMPs will be able to use a shared SMP provided by one of the partners with an available SMP. In such cases, the routing information of those partners will be stored in this shared SMP.
*'''PRE2a:''' Imaginary participants
**IDK: Central IAL. Its information is automatically updated and fed from the SMPs connected to it.
**SMP: shared SMP of the Playground IT2. It returns the routing information of the targeted Connector (DR/DT) of the Playground IT2.
*'''PRE2b:''' Simulated data from real participants
**IDK: Central IAL. Its information is automatically updated and fed from the SMPs connected to it.
**SMP: national SMP of the requested participant. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.
*'''PRO2:''' Real data from real participants
**IDK: Central IAL. Its information is automatically updated and fed from the SMPs connected to it.
**SMP: national SMP of the requested participant. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.

Summary of software interfaces.

2022-10-04T14:35:23Z

Javier.ferrero: Javier.ferrero moved page Summary of software interfaces. to Summary of software interfaces: To remove the period from the title.

#REDIRECT [[Summary of software interfaces]]

Summary of software interfaces

2022-10-04T14:35:23Z

Javier.ferrero: Javier.ferrero moved page Summary of software interfaces. to Summary of software interfaces: To remove the period from the title.

== Available interfaces ==
{| class="wikitable"
|+DE4A Components interfaces description (Iteration 2)
!Component
!Pattern
!Service
!Referenced API
!Interface type
!Communication
!Input message
!Output
|-
| rowspan="3" |Data Evaluator
| rowspan="2" |[https://wiki.de4a.eu/index.php/User-supported_intermediation_pattern_communication_diagram USI]
|* Forward evidence
|/requestForwardEvidence
|XML REST
|Asynchronous
|[https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseExtractMultiEvidenceType ResponseExtractMultiEvidenceType]
|[https://github.com/de4a-wp5/xml-schemas/blob/4d074ee82355255293a0c9e071d9507920f0af02/XSD/de4a/common-types.xsd#L191 ACK]
|-
|* Response user redirection
|/responseUserRedirection
|XML REST
|Asynchronous
|[https://wiki.de4a.eu/index.php/Data_Dictionary#RedirectUserType RedirectUserType]
|HTTP Status 302/303 (Http/1 Http/2)
|-
|S&N
|Event Notificacion
|/notificationEvent
|XML REST
|Asynchronous
|[https://wiki.de4a.eu/index.php/Data_Dictionary#EventNotificationType EventNotificationType]
|[https://github.com/de4a-wp5/xml-schemas/blob/4d074ee82355255293a0c9e071d9507920f0af02/XSD/de4a/common-types.xsd#L191 ACK]
|-
| rowspan="5" |Data Owner
|[https://wiki.de4a.eu/index.php/Intermediation_pattern_communication_diagram IM]
|Extract evidence IM
|/request/im/
|XML REST
|Asynchronous
|[https://wiki.de4a.eu/index.php/Data_Dictionary#RequestExtractMultiEvidenceIMType RequestExtractMultiEvidenceIMType]
|[https://github.com/de4a-wp5/xml-schemas/blob/4d074ee82355255293a0c9e071d9507920f0af02/XSD/de4a/common-types.xsd#L191 ACK]
|-
| rowspan="2" |[https://wiki.de4a.eu/index.php/User-supported_intermediation_pattern_communication_diagram USI]
|Extract evidence USI
|/request/usi/
|XML REST
|Asynchronous
|[https://wiki.de4a.eu/index.php/Data_Dictionary#RequestExtractMultiEvidenceUSIType RequestExtractMultiEvidenceUSIType]
|[https://github.com/de4a-wp5/xml-schemas/blob/4d074ee82355255293a0c9e071d9507920f0af02/XSD/de4a/common-types.xsd#L191 ACK]
|-
|RequestUserRedirection
|/requestUserRedirection
|XML REST
|Asynchronous
|[https://wiki.de4a.eu/index.php/Data_Dictionary#RedirectUserType RedirectUserType]
|HTTP Status 302/303 (Http/1 Http/2)
|-
|[https://wiki.de4a.eu/index.php/Lookup_pattern_communication_diagram LU]
|Lookup
|/requestExtractMultiEvidenceLU
|XML REST
|Asynchronous
|[https://wiki.de4a.eu/index.php/Data_Dictionary#RequestExtractMultiEvidenceLUType RequestExtractMultiEvidenceLUType]
|[https://github.com/de4a-wp5/xml-schemas/blob/4d074ee82355255293a0c9e071d9507920f0af02/XSD/de4a/common-types.xsd#L191 ACK]
|-
|S&N
|Event Subscription
|/requestEventSubscription
|XML REST
|Asynchronous
|[https://wiki.de4a.eu/index.php/Data_Dictionary#RequestEventSubscriptionType RequestEventSubscriptionType]
|[https://github.com/de4a-wp5/xml-schemas/blob/4d074ee82355255293a0c9e071d9507920f0af02/XSD/de4a/common-types.xsd#L191 ACK]
|-
| rowspan="5" |Data Requestor (Connector)
|[https://wiki.de4a.eu/index.php/Intermediation_pattern_communication_diagram IM]
[https://wiki.de4a.eu/index.php/User-supported_intermediation_pattern_communication_diagram USI]
|Lookup Routing Information
|/service/ial/
|XML REST
|Synchronous
|All the necessary parameters will be in the URL. It will be a comma-separated canonical evidence identifier collection (up to 20) followed by the AtuCode.
|[https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseLookupRoutingInformationType ResponseLookupRoutingInformationType]
|-
|[https://wiki.de4a.eu/index.php/Intermediation_pattern_communication_diagram IM]
|Extract evidence IM
|/request/im/
|XML REST
|Asynchronous
|[https://wiki.de4a.eu/index.php/Data_Dictionary#RequestExtractMultiEvidenceIMType RequestExtractMultiEvidenceIMType]
|[https://github.com/de4a-wp5/xml-schemas/blob/4d074ee82355255293a0c9e071d9507920f0af02/XSD/de4a/common-types.xsd#L191 ACK]
|-
|[https://wiki.de4a.eu/index.php/User-supported_intermediation_pattern_communication_diagram USI]
|Extract evidence USI
|/request/usi/
|XML REST
|Asynchronous
|[https://wiki.de4a.eu/index.php/Data_Dictionary#RequestExtractMultiEvidenceUSIType RequestExtractMultiEvidenceUSIType]
|[https://github.com/de4a-wp5/xml-schemas/blob/4d074ee82355255293a0c9e071d9507920f0af02/XSD/de4a/common-types.xsd#L191 ACK]
|-
|[https://wiki.de4a.eu/index.php/Lookup_pattern_communication_diagram LU]
|Lookup
|/requestTransferEvidenceLU
|XML REST
|Asynchronous
|[https://wiki.de4a.eu/index.php/Data_Dictionary#RequestExtractMultiEvidenceLUType RequestExtractMultiEvidenceLUType]
|[https://github.com/de4a-wp5/xml-schemas/blob/4d074ee82355255293a0c9e071d9507920f0af02/XSD/de4a/common-types.xsd#L191 ACK]
|-
|S&N
|Event Subscription
|/requestEventSubscription
|XML REST
|Asynchronous
|[https://wiki.de4a.eu/index.php/Data_Dictionary#RequestEventSubscriptionType RequestEventSubscriptionType]
|[https://github.com/de4a-wp5/xml-schemas/blob/4d074ee82355255293a0c9e071d9507920f0af02/XSD/de4a/common-types.xsd#L191 ACK]
|-
| rowspan="4" |Data Transferor (Connector)
|[https://wiki.de4a.eu/index.php/User-supported_intermediation_pattern_communication_diagram USI]
[https://wiki.de4a.eu/index.php/Intermediation_pattern_communication_diagram IM]

[https://wiki.de4a.eu/index.php/Lookup_pattern_communication_diagram LU]
|Response transfer evidence
|/responseTransferEvidence
|XML REST
|Asynchronous
|[https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseExtractMultiEvidenceType ResponseExtractMultiEvidenceType]
|[https://github.com/de4a-wp5/xml-schemas/blob/4d074ee82355255293a0c9e071d9507920f0af02/XSD/de4a/common-types.xsd#L191 ACK]
|-
|[https://wiki.de4a.eu/index.php/User-supported_intermediation_pattern_communication_diagram USI]
|* Response user redirection
|/usiRedirectUser
|XML REST
|Asynchronous
|[https://wiki.de4a.eu/index.php/Data_Dictionary#RedirectUserType RedirectUserType]
|[https://github.com/de4a-wp5/xml-schemas/blob/4d074ee82355255293a0c9e071d9507920f0af02/XSD/de4a/common-types.xsd#L191 ACK]
|-
|S&N
|Event Subscription
|/responseEventSubscription
|XML REST
|Asynchronous
|[https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseEventSubscriptionType ResponseEventSubscriptionType]
|[https://github.com/de4a-wp5/xml-schemas/blob/4d074ee82355255293a0c9e071d9507920f0af02/XSD/de4a/common-types.xsd#L191 ACK]
|-
|S&N
|Event Notificacion
|/notificationEvent
|XML REST
|Asynchronous
|[https://wiki.de4a.eu/index.php/Data_Dictionary#EventNotificationType EventNotificationType]
|[https://github.com/de4a-wp5/xml-schemas/blob/4d074ee82355255293a0c9e071d9507920f0af02/XSD/de4a/common-types.xsd#L191 ACK]
|}

Useful information on pilots and participants

2022-09-13T12:17:32Z

Javier.ferrero: /* DE4A pilot participants IT2 */

Useful information about the pilots and the participants in DE4A during the second iteration of the project. This information is intended to serve as a reference for the configuration and operation of the partners' infrastructures and the Playground. Each partner is responsible for entering and keeping the information collected on this Wiki page up-to-date.

== Progress of the deployment of DE4A participants' infrastructures in iteration 2 ==

=== SMP in Member States ===
{| class="wikitable"
!MS
!Member State
!Participant
!Own SMP (Deployed & configured / In progress / No, planned for X)
|-
|'''AT'''
|Austria
|BRZ
|Deployed and configured, phoss 5.7.1, Telesec Certificates
|-
|'''ES'''
| Spain
|SGAD
| Deployed and configured: phoss SMP v5.6.2
|-
|'''LU'''
|Luxembourg
|CTIE
|Not deployed, prevision "before light review"
|-
|'''NL'''
|The Netherlands
|RVO
|Deployed, solving configuration issues
|-
|'''PT'''
| Portugal
|AMA
|Deployed and configured in test environment. Security Audit findings in discussion for deployment to PPR
|-
|'''RO'''
| Romania
|ONRC
|Deployed and configured
|-
|'''RO'''
| Romania
|MoAI
|Not yet deployed
|-
|'''SU'''
|Sweden
|BVE
|Deployed and configured
|-
|'''SI'''
| Slovenia
|SI-MPA
|Deployed and configured to use IAL, configuration verified by Philip
|}

===DE4A Connector in Member States===
{| class="wikitable"
!MS
!Member State
!Participant
!Own Connector (Deployed & configured / In progress / No, planned for X)
|-
|'''AT'''
|Austria
|BRZ
|
|-
|'''ES'''
|Spain
|SGAD
|Deployed & configured: v0.2.6
|-
|'''LU'''
|Luxembourg
|CTIE
|
|-
|'''NL'''
|The Netherlands
|RVO
|
|-
|'''PT'''
|Portugal
|AMA
|
|-
|'''RO'''
| Romania
|ONRC
|
|-
|'''RO'''
|Romania
|MoAI
|
|-
|'''SU'''
|Sweden
|BVE
|
|-
|'''SI'''
|Slovenia
|SI-MPA
|Deployed & configured: v0.2.6
|}
== Summary of pilots and participants during the second iteration ==

=== Summary of DE4A pilots IT2 ===
{| class="wikitable"
! colspan="5" |Iteration 2
|-
|'''Pilot'''
|'''Use case'''
|'''Use case name'''
|'''Interaction pattern used'''
|'''Evidence exchanged'''
|-
| rowspan="3" |'''Studying abroad (SA)'''
|UC1.1
|Application to public higher education
|User-Supported Intermediation (USI)
|Higher Education Diploma
Secondary Education Diploma
|-
|UC1.2
|Applying for study grant
|User-Supported Intermediation (USI)
|Higher Education Diploma
Large Family Evidence

Disability Evidence
|-
|UC1.3
|Diploma / Certs / Studies / Professional recognition
|Verifiable Credentials (VC)
|Higher Education Diploma
|-
| rowspan="2" |'''Doing business abroad (DBA)'''
|UC2.1
|Starting a business in another Member State
|Intermediation (IM)
Subscription and Notification (S&N)
|Company Registration
|-
|UC2.2
|Doing business in another Member State
|Intermediation (IM)
Subscription and Notification (S&N)

Lookup (LU)
|Company Registration
|-
| rowspan="2" |'''Moving abroad (MA)'''
|UC3.1
|Request address change
|Registration: User-Supported Intermediation (USI)
Deregistration: Notification (S&N) and Lookup (LU)
|Domicile Registration Evidence
|-
|UC3.2
|Request an extract or copy of civil state certificate
|User-Supported Intermediation (USI)
|Birth Evidence
Marriage Evidence
|}

=== DE4A pilot participants IT2 ===
{| class="wikitable"
! colspan="4" |Partner
! colspan="3" |SA
! colspan="2" |DBA
! colspan="2" |MA
!
|-
|'''Short name'''
|'''Name'''
|'''Country'''
|'''Participant ID'''
|'''UC1.1'''
|'''UC1.2'''
|'''UC1.3'''
|'''UC2.1'''
|'''UC2.2'''
|'''UC3.1'''
|'''UC3.2'''
|'''Notes'''
|-
|BMDW
|Bundesministerium fuer Digitalisierung und Wirtschaftsstandort
|AT
|iso6523-actorid-upis::9991:at000000271
|
|
|
|DE
DO
|DE

DO
|
|
|
|-
|BRZ
|Bundesrechenzentrum GMBH (Federal Data Center)
|AT
|
|
|
|
|DR
DT
|DR

DT
|
|
|BRZ has no Participant ID, because it is only DR and DT
|-
|SGAD
|Secretaría General de Administración Digital (General Secretariat for Digital Administration)
|ES
|iso6523-actorid-upis::9920:ess2833002e
|DR
DO,DT
|DO,DT
|DP
|
|
|DO,DT
|DE,DR
DO,DT
|Evidence in SA UCs is provided by the DE4A partner UJI.
|-
|UJI
|Universitat Jaume I de Castellón (Jaume I University of Castellón)
|ES
|iso6523-actorid-upis::9920:esq6250003h
|DE*
|
|
|
|
|
|
|*Connector provided by SGAD. UJI is also an evidence provider in all SA UCs through SGAD.
|-
|CTIE
|Centre des Technologies de l'Information de l'Etat (State Information Technology Center)
|LU
|iso6523-actorid-upis::9991:lu000000025
|
|
|
|
|
|DE,DR
DO,DT
|DE,DR
DO,DT
|
|-
|RVO
|Rijksdienst voor Ondernemend Nederland (Netherlands Enterprise Agency)
|NL
|iso6523-actorid-upis::9991:nl000000024
|
|
|
|DE,DR

DO,DT
|DE,DR

DO,DT
|
|
|
|-
|AMA-IP
|Agencia para a Modernizacao Administrativa IP (Administration Modernization Agency)
|PT
|iso6523-actorid-upis::9991:pt000000026
|DR
DO,DT
|DT
|
|
|
|DR
DO,DT
|DR
|AMA-IP consults INESC-ID in some cases when the latter takes the role of DO. Therefore, INESC-ID does not directly take part of the DE4A network as DO, but AMA-IP instead.
|-
|INESC-ID
|Institute for Systems and Computer Engineering, Technology and Science
|PT
|iso6523-actorid-upis::9991:pt990000101
|DE
|
|DC
DP
|
|
|
|
|
|-
|MoAI
|Ministerul Afacerilor Interne (Ministry of Internal Affairs)
|RO
|iso6523-actorid-upis::9991:ro000000005
|
|
|
|
|
|DE,DR

DO,DT
|DE,DR

DO,DT
|
|-
|ORNC
|Oficiul National B22 al Registrului Comertului
|RO
|iso6523-actorid-upis::9991:ro000000006
|
|
|
|DE,DR

DO,DT
|DE,DR

DO,DT
|
|
|
|-
|BVE
|Bolagsverket (Companies Registration Office)
|SE
|iso6523-actorid-upis::9991:se000000013
|
|
|
|DE,DR
|DE,DR
|
|
|
|-
|JSI
|Institut "Jožef Stefan" (Jožef Stefan Institute)
|SI
|iso6523-actorid-upis::9949:si55560822
|
|DE
|
|
|
|
|
|
|-
|MIZŠ
|Ministrstvo za izobraževanje, znanost in šport (Ministry of Education, Science and Sport)
|SI
|iso6523-actorid-upis::9949:si14246821
|DE
DO
|
|DC
DP
|
|
|
|
|*The central preview functionality for DO is provided by SI-MPA.
|-
|SI-MPA
|Ministrstvo za javno upravo (Ministry of Public Administration)
|SI
|iso6523-actorid-upis::9991:si000000015
|DR
DT
|DR
|
|
|
|DR,DT
|DR,DT
|
|-
|MNZ
|Ministrstvo za notranje zadeve (Ministry of the Interior)
|SI
|iso6523-actorid-upis::9949:si52817652
|
|
|
|
|
|DO
|DO
|*The central preview functionality for DO is provided by SI-MPA.
|}

=== Technical information on participants IT2 ===
{| class="wikitable"
!
==== Test domain (Playground) ====
!
==== Pilot domain ====
|-
|
{| class="wikitable"
! colspan="4" |SMP
|-
|'''Country'''
|'''Participant'''
|'''SMP endpoint'''
|'''SMP certificate'''
|-
|ES (shared)
|SGAD
|[https://de4a.redsara.es/sgad-smp https://de4a.redsara.es/sgad-smp/]
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD owncloud folder]
|}
|
{| class="wikitable"
! colspan="4" |SMP
|-
|'''Country'''
|'''Participant'''
|'''SMP endpoint'''
|'''SMP certificate'''
|-
|AT
|BRZ
|https://de4a-smp.usp.gv.at/
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD&fileid=1169370 owncloud folder]
|-
|ES
|SGAD
|
|
|-
|LU
|
|
|
|-
|NL
|
|
|
|-
|PT
|
|
|
|-
|RO
|
|
|
|-
|SE
|
|
|
|-
|SI
|SI-MPA
|https://toop-smp.pprod.medius.si/public
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SI-MPA owncloud folder]
|}
|-
|
{| class="wikitable"
! colspan="3" |DE
|-
|'''Participant'''
|'''Evidence types consumed'''
|'''DE e-procedure portal'''
|-
|BMDW
|Company Registration
|
|-
|SGAD
|Birth Evidence
Marriage Evidence
|
|-
|UJI
|Higher Education Diploma
|
|-
|CTIE
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|RVO
|Company Registration
|
|-
|INESC-ID
|Higher Education Diploma
Secondary Education Diploma
|
|-
|
|
|
|-
|MoAI
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|ORNC
|Company Registration
|
|-
|BVE
|Company Registration
|
|-
|JSI
|Higher Education Diploma
Large Family Evidence

Disability Evidence
|https://grants.e5.ijs.si/grants/public/
|-
|MIZŠ
|Higher Education Diploma
Secondary Education Diploma
|http://srvas2.rrc.si/prijava/?lang=en
|}
|
{| class="wikitable"
! colspan="3" |DE
|-
|'''Participant'''
|'''Evidence types consumed'''
|'''DE e-procedure portal'''
|-
|BMDW
|Company Registration
|
|-
|SGAD
|Birth Evidence
Marriage Evidence
|
|-
|UJI
|Higher Education Diploma
|
|-
|CTIE
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|RVO
|Company Registration
|
|-
|INESC-ID
|Higher Education Diploma
Secondary Education Diploma
|
|-
|
|
|
|-
|MoAI
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|ORNC
|Company Registration
|
|-
|BVE
|Company Registration
|
|-
|JSI
|Higher Education Diploma
Large Family Evidence

Disability Evidence
|
|-
|MIZŠ
|Higher Education Diploma
Secondary Education Diploma
|
|}
|-
|
{| class="wikitable"
! colspan="3" |DO
|-
|'''Participant'''
|'''Evidence types provided'''
|'''DO evidence portal'''
|-
|BMDW
|Company Registration
|
|-
|SGAD
|Higher Education Diploma
Secondary Education Diploma

Large Family Evidence

Disability Evidence

Domicile Registration Evidence

Birth Evidence

Marriage Evidence

Pension Evidence

Unemployment Evidence

Working Life Evidence
|
|-
|CTIE
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|RVO
|Company Registration
|
|-
|AMA-IP
|Domicile Registration Evidence
|
|-
|INESC-ID
|Higher Education Diploma
|
|-
|MoAI
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|ORNC
|Company Registration
|
|-
|MIZŠ
|Higher Education Diploma
|Direct public access is not enabled
|-
|MNZ
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|Direct public access is not enabled
|}
|
{| class="wikitable"
! colspan="3" |DO
|-
|'''Participant'''
|'''Evidence types provided'''
|'''DO evidence portal'''
|-
|BMDW
|Company Registration
|
|-
|SGAD
|Higher Education Diploma
Secondary Education Diploma

Large Family Evidence

Disability Evidence

Domicile Registration Evidence

Birth Evidence

Marriage Evidence

Pension Evidence

Unemployment Evidence

Working Life Evidence
|
|-
|CTIE
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|RVO
|Company Registration
|
|-
|AMA-IP
|Domicile Registration Evidence
|
|-
|INESC-ID
|Higher Education Diploma
|
|-
|MoAI
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|ORNC
|Company Registration
|
|-
|MIZŠ
|Higher Education Diploma
|Direct public access is not enabled
|-
|MNZ
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|Direct public access is not enabled
|}
|-
|
{| class="wikitable"
! colspan="3" |DR
|-
|'''Participant'''
|'''AS4 certificate'''
|'''Connector endpoint'''
|-
|BRZ
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD&fileid=1169370 owncloud folder]
|https://de4a.usp.gv.at/ado/phase4
|-
|SGAD
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD owncloud folder]
|https://pre-as4gw-dt-de4a.redsara.es/de4a-it2-connector/
|-
|CTIE
|
|
|-
|RVO
|
|
|-
|AMA-IP
|
|
|-
|ORNC
|
|
|-
|BVE
|
|
|-
|SI-MPA
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SI-MPA owncloud folder]
|https://toop-as4.pprod.medius.si/
|}
|
{| class="wikitable"
! colspan="3" |DR
|-
|'''Participant'''
|'''AS4 certificate'''
|'''Connector endpoint'''
|-
|SGAD
|
|
|-
|CTIE
|
|
|-
|RVO
|
|
|-
|AMA-IP
|
|
|-
|ORNC
|
|
|-
|BVE
|
|
|-
|SI-MPA
|
|
|}
|-
|
{| class="wikitable"
! colspan="3" |DT
|-
|'''Participant'''
|'''AS4 certificate'''
|'''Connector endpoint'''
|-
|BRZ
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD&fileid=1169370 owncloud folder]
|https://de4a.usp.gv.at/ado/phase4
|-
|SGAD
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD owncloud folder]
|https://pre-as4gw-dt-de4a.redsara.es/de4a-it2-connector/
|-
|CTIE
|
|
|-
|RVO
|
|
|-
|AMA-IP
|
|
|-
|MoAI
|
|
|-
|ORNC
|
|
|-
|SI-MPA
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SI-MPA owncloud folder]
|https://toop-as4.pprod.medius.si/
|}
|
{| class="wikitable"
! colspan="3" |DT
|-
|'''Participant'''
|'''AS4 certificate'''
|'''Connector endpoint'''
|-
|BRZ
|
|
|-
|SGAD
|
|
|-
|CTIE
|
|
|-
|RVO
|
|
|-
|AMA-IP
|
|
|-
|MoAI
|
|
|-
|ORNC
|
|
|-
|SI-MPA
|
|
|}
|}

===DE-DO.json participant endpoint urls===
{| class="wikitable"
!
====Test domain (PRE2b) ====
!
====Pilot domain (PRO2)====
|-
|
{| class="wikitable"
! colspan="5" |Data Owners
|-
|'''Country'''
|'''Participant'''
|'''Participant ID'''
|'''Pattern'''
|'''DO Endpoint URL'''
|-
| rowspan="4" |AT
| rowspan="4" |
| rowspan="4" |iso6523-actorid-upis::99XX:at000000271-test-it2
|IM
|
|-
|USI
|
|-
| LU
|
|-
|SN
|
|-
| rowspan="4" | ES
| rowspan="4" |SGAD
| rowspan="4" |iso6523-actorid-upis::9920:ess2833002e-test-it2
|IM
|https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/requestExtractEvidenceIM
|-
|USI
|https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/do1/usi/extractevidence
|-
|LU
|https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/dataOwner/in/lu/
|-
|SN
|https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/dataOwner/in/sn/
|-
| rowspan="4" |PT
| rowspan="4" |AMA
| rowspan="4" | iso6523-actorid-upis::99XX:pt000000026-test-it2
|IM
|
|-
|USI
|
|-
| LU
|
|-
|SN
|
|-
| rowspan="4" |NL
| rowspan="4" |RVO
| rowspan="4" |iso6523-actorid-upis::99XX:nl000000024-test-it2
|IM
|
|-
|USI
|
|-
|LU
|
|-
|SN
|
|-
| rowspan="4" |SI
| rowspan="4" |MIZŠ
| rowspan="4" |iso6523-actorid-upis::9949:si14246821
|IM
|N/A
|-
|USI
|Not publicly disclosed
|-
|LU
|N/A
|-
|SN
|N/A
|-
|SI
|MNZ
|iso6523-actorid-upis::9949:si52817652
|USI
|Not publicly disclosed
|-
| rowspan="4" |SE
| rowspan="4" |BVE
| rowspan="4" |iso6523-actorid-upis::99XX:se000000013-test-it2
|IM
|
|-
|USI
|
|-
|LU
|
|-
|SN
|
|}
{| class="wikitable"
! colspan="5" |Data Evaluators
|-
|'''Country'''
|'''Participant'''
|'''Participant ID'''
|'''Response Type'''
|'''DE Endpoint URL'''
|-
| rowspan="4" | AT
| rowspan="4" |
| rowspan="4" |iso6523-actorid-upis::99XX:at000000271-test-it2
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" |ES
| rowspan="4" |SGAD
| rowspan="4" |iso6523-actorid-upis::9920:ess2833002e-test-it2
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" | ES
| rowspan="4" |UJI
| rowspan="4" |iso6523-actorid-upis::9920:esq6250003h-test-it2
|response
|
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |PT
| rowspan="4" | INESC-ID
| rowspan="4" |iso6523-actorid-upis::9991:pt990000101-test-it2
|response
|
|-
|subscription_resp
| N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |NL
| rowspan="4" |RVO
| rowspan="4" |iso6523-actorid-upis::99XX:nl000000024-test-it2
|response
|N/A
|-
|subscription_resp
| N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |MIZŠ
| rowspan="4" |iso6523-actorid-upis::9949:si14246821
|response
|http://srvas2.rrc.si/de4a/requestForwardEvidence
|-
|subscription_resp
|N/A
|-
|redirect
|http://srvas2.rrc.si/de4a/redirectUser
|-
|notification
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |JSI
| rowspan="4" |iso6523-actorid-upis::9949:si55560822-test-it2
| response
| https://grants.e5.ijs.si/grants/public/de-r/requestForwardEvidence
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |SE
| rowspan="4" |BVE
| rowspan="4" |iso6523-actorid-upis::99XX:se000000013-test-it2
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|}
|
{| class="wikitable"
! colspan="5" |Data Owners
|-
|'''Country'''
|'''Participant'''
|'''Participant ID'''
|'''Pattern'''
|'''DO Endpoint URL'''
|-
| rowspan="4" |AT
| rowspan="4" |
| rowspan="4" |
|IM
|N/A
|-
|USI
|N/A
|-
| LU
|N/A
|-
|SN
|N/A
|-
| rowspan="4" | ES
| rowspan="4" |SGAD
| rowspan="4" |
|IM
|N/A
|-
|USI
|N/A
|-
|LU
|N/A
|-
|SN
|N/A
|-
| rowspan="4" |PT
| rowspan="4" |AMA
| rowspan="4" |
|IM
| N/A
|-
|USI
|N/A
|-
| LU
| N/A
|-
|SN
|N/A
|-
| rowspan="4" |NL
| rowspan="4" |RVO
| rowspan="4" |
|IM
|N/A
|-
|USI
|N/A
|-
|LU
|N/A
|-
|SN
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |MIZŠ
| rowspan="4" |iso6523-actorid-upis::9949:si14246821
|IM
|N/A
|-
|USI
|Not publicly disclosed
|-
|LU
|N/A
|-
|SN
|N/A
|-
|SI
|MNZ
|iso6523-actorid-upis::9949:si52817652
|USI
|Not publicly disclosed
|-
| rowspan="4" |SE
| rowspan="4" |BVE
| rowspan="4" |
|IM
|N/A
|-
|USI
|N/A
|-
|LU
|N/A
|-
|SN
|N/A
|}
{| class="wikitable"
! colspan="5" |Data Evaluators
|-
|'''Country'''
|'''Participant'''
|'''Participant ID'''
|'''Response Type'''
|'''DE Endpoint URL'''
|-
| rowspan="4" | AT
| rowspan="4" |
| rowspan="4" |
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" |ES
| rowspan="4" |SGAD
| rowspan="4" |
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" | ES
| rowspan="4" |UJI
| rowspan="4" |
|response
|
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |PT
| rowspan="4" | INESC-ID
| rowspan="4" |
|response
|
|-
|subscription_resp
| N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |NL
| rowspan="4" |RVO
| rowspan="4" |
|response
|N/A
|-
|subscription_resp
| N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |MIZŠ
| rowspan="4" |iso6523-actorid-upis::9949:si14246821
|response
|
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |JSI
| rowspan="4" |iso6523-actorid-upis::9949:si55560822
| response
|
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |SE
| rowspan="4" |BVE
| rowspan="4" |
|response
| N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|}

|}

==DE4A infrastructure IT2==
===Playground infrastructure IT2===
The following diagram depicts the Playground infrastructure for the second iteration, with the deployment of its corresponding components.[[File:DE4A network IT2-Playground IT2.drawio.png|frame|alt=|none]]

===Pilot partners infrastructure flavours IT2 ===
The following two diagrams outline the general infrastructure expected from the Member States and partners involved in the pilots. Each Connector is in turn connected and exchanges data with the corresponding Connector (DR or DT) of the Playground or other partners.

At this stage, all DE4A participants are expected to follow the set-up A, while only Romania is expected to follow set-up B.[[File:DE4A network IT2-Country set-up A.drawio.png|frame|alt=|left]]

[[File:DE4A network IT2-Country set-up B.drawio.png|frame|alt=|none]]

== Domains and types of participant IDs ==

===DE4A domains===
In DE4A, there are two types of participants:

*Imaginary participants: intended to query the examples stored in the Mocked DO.
*Real participants: intended to retrieve data directly returned by partners.

At the same time, for the real participants, there are also two “domains”:

*Test domain: only fake data is used for test purposes. It is the domain related to the DE4A Playground, where participants return datasets from test sources.
*Pilot domain: real data from real citizens and companies is supposed to be used. It is the environment used for the running phase of the pilots, where participants access to their real registries and return real evidence from them.

Finally, the project is divided into two iterations where each of them needs a copy of those two domains, and where some overlap between them occurs.
[[File:Domain overlap.png|none|thumb|910x910px]]
As the DE4A project uses the dynamic discovery of eDelivery, where there cannot be duplicate participant IDs targeting to different Connectors (depending on the domain concerned), we need to define a different participant ID schema per each domain:

*'''PRE1a''': Imaginary participants stored in the Mocked DO for iteration 1 for testing. The related evidence is stored in the Mocked DO deployed in SGAD (ES).
** Scheme identifier used: “'''9999'''”.
** Suffix used: “'''-it1'''”.
**E.g. iso6523-actorid-upis::99'''99''':ess2833002e'''-it1'''

*'''PRE1b:''' Simulated data returned by the real participants used for testing in Playground iteration 1. The related evidence is located in each partner’s infrastructure, within their test domain.
**Scheme identifier used: “'''99XX'''”, where “XX” depends on the identifier each participant is using.
**Suffix used: “'''-it1'''”.
**E.g. iso6523-actorid-upis::99'''20''':ess2833002e'''-it1'''
*'''PRO1:''' Real data returned by the real participants during the execution of phase 1 of the pilot. The related evidence is located in each partner’s infrastructure, within their pilot domain.
**Scheme identifier used: “'''99XX'''”, where “XX” depends on the identifier each participant is using. It is the “real” participant ID.
**Suffix used: ''none'', since there is no overlap between phases 1 and 2 of the pilots.
**E.g. iso6523-actorid-upis::99'''20''':ess2833002e
*'''PRE2a:''' Imaginary participants stored in the Mocked DO for iteration 2 for testing. The related evidence is stored in the Mocked DO deployed in SGAD (ES).
**Scheme identifier used: “'''9999'''”.
**Suffix used: “'''-mock-it2'''”.
**E.g. iso6523-actorid-upis::99'''99''':ess2833002e'''-mock-it2'''
*'''PRE2b:''' Simulated data returned by the real participants used for testing in Playground iteration 2. The related evidence is located in each partner’s infrastructure, within their test domain.
**Scheme identifier used: “'''99XX'''”, where “XX” depends on the identifier each participant is using.
**Suffix used: “'''-test-it2'''”.
**E.g. iso6523-actorid-upis::99'''20''':ess2833002e'''-test-it2'''
*'''PRO2:''' Real data returned by the real participants during the execution of phase 2 of the pilot. The related evidence is located in each partner’s infrastructure, within their pilot domain.
**Scheme identifier used: “'''99XX'''”, where “XX” depends on the identifier each participant is using. It is the “real” participant ID.
**Suffix used: ''none'', since there is no overlap between phases 1 and 2 of the pilots.
**E.g. iso6523-actorid-upis::99'''20''':ess2833002e

Therefore, DE4A domains are differentiated by the participant ID schema used.

===Location of the participant IDs===
These different participant IDs must be stored in their corresponding IDKs and SMPs and configured to return the proper information:

*'''PRE1a:''' Imaginary participants
**IDK: none (for these participants, the mocked DE knows which the imaginary participants are and which DO to query, namely, the mocked DO of the first iteration).
**SMP: shared SMP of the Playground IT1. It returns the routing information of the targeted Connector (DR/DT) of the Playground IT1.
*'''PRE1b''': Simulated data from real participants
**IDK: mocked IDK of the Playground IT1.
**SMP: shared SMP of the Playground IT1. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.
*'''PRO1:''' Real data from real participants
**IDK: mocked IDK of the pilot running environment.
**SMP: national SMP of the requested participant. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.
***For the first pilot running phase, partners who have not yet deployed their own SMPs will be able to use a shared SMP provided by one of the partners with an available SMP. In such cases, the routing information of those partners will be stored in this shared SMP.
*'''PRE2a:''' Imaginary participants
**IDK: Central IAL. Its information is automatically updated and fed from the SMPs connected to it.
**SMP: shared SMP of the Playground IT2. It returns the routing information of the targeted Connector (DR/DT) of the Playground IT2.
*'''PRE2b:''' Simulated data from real participants
**IDK: Central IAL. Its information is automatically updated and fed from the SMPs connected to it.
**SMP: national SMP of the requested participant. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.
*'''PRO2:''' Real data from real participants
**IDK: Central IAL. Its information is automatically updated and fed from the SMPs connected to it.
**SMP: national SMP of the requested participant. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.

Useful information on pilots and participants

2022-09-13T12:16:57Z

Javier.ferrero: Modification of AMA and INESC's participation in pilots.

Useful information about the pilots and the participants in DE4A during the second iteration of the project. This information is intended to serve as a reference for the configuration and operation of the partners' infrastructures and the Playground. Each partner is responsible for entering and keeping the information collected on this Wiki page up-to-date.

== Progress of the deployment of DE4A participants' infrastructures in iteration 2 ==

=== SMP in Member States ===
{| class="wikitable"
!MS
!Member State
!Participant
!Own SMP (Deployed & configured / In progress / No, planned for X)
|-
|'''AT'''
|Austria
|BRZ
|Deployed and configured, phoss 5.7.1, Telesec Certificates
|-
|'''ES'''
| Spain
|SGAD
| Deployed and configured: phoss SMP v5.6.2
|-
|'''LU'''
|Luxembourg
|CTIE
|Not deployed, prevision "before light review"
|-
|'''NL'''
|The Netherlands
|RVO
|Deployed, solving configuration issues
|-
|'''PT'''
| Portugal
|AMA
|Deployed and configured in test environment. Security Audit findings in discussion for deployment to PPR
|-
|'''RO'''
| Romania
|ONRC
|Deployed and configured
|-
|'''RO'''
| Romania
|MoAI
|Not yet deployed
|-
|'''SU'''
|Sweden
|BVE
|Deployed and configured
|-
|'''SI'''
| Slovenia
|SI-MPA
|Deployed and configured to use IAL, configuration verified by Philip
|}

===DE4A Connector in Member States===
{| class="wikitable"
!MS
!Member State
!Participant
!Own Connector (Deployed & configured / In progress / No, planned for X)
|-
|'''AT'''
|Austria
|BRZ
|
|-
|'''ES'''
|Spain
|SGAD
|Deployed & configured: v0.2.6
|-
|'''LU'''
|Luxembourg
|CTIE
|
|-
|'''NL'''
|The Netherlands
|RVO
|
|-
|'''PT'''
|Portugal
|AMA
|
|-
|'''RO'''
| Romania
|ONRC
|
|-
|'''RO'''
|Romania
|MoAI
|
|-
|'''SU'''
|Sweden
|BVE
|
|-
|'''SI'''
|Slovenia
|SI-MPA
|Deployed & configured: v0.2.6
|}
== Summary of pilots and participants during the second iteration ==

=== Summary of DE4A pilots IT2 ===
{| class="wikitable"
! colspan="5" |Iteration 2
|-
|'''Pilot'''
|'''Use case'''
|'''Use case name'''
|'''Interaction pattern used'''
|'''Evidence exchanged'''
|-
| rowspan="3" |'''Studying abroad (SA)'''
|UC1.1
|Application to public higher education
|User-Supported Intermediation (USI)
|Higher Education Diploma
Secondary Education Diploma
|-
|UC1.2
|Applying for study grant
|User-Supported Intermediation (USI)
|Higher Education Diploma
Large Family Evidence

Disability Evidence
|-
|UC1.3
|Diploma / Certs / Studies / Professional recognition
|Verifiable Credentials (VC)
|Higher Education Diploma
|-
| rowspan="2" |'''Doing business abroad (DBA)'''
|UC2.1
|Starting a business in another Member State
|Intermediation (IM)
Subscription and Notification (S&N)
|Company Registration
|-
|UC2.2
|Doing business in another Member State
|Intermediation (IM)
Subscription and Notification (S&N)

Lookup (LU)
|Company Registration
|-
| rowspan="2" |'''Moving abroad (MA)'''
|UC3.1
|Request address change
|Registration: User-Supported Intermediation (USI)
Deregistration: Notification (S&N) and Lookup (LU)
|Domicile Registration Evidence
|-
|UC3.2
|Request an extract or copy of civil state certificate
|User-Supported Intermediation (USI)
|Birth Evidence
Marriage Evidence
|}

=== DE4A pilot participants IT2 ===
{| class="wikitable"
! colspan="4" |Partner
! colspan="3" |SA
! colspan="2" |DBA
! colspan="2" |MA
!
|-
|'''Short name'''
|'''Name'''
|'''Country'''
|'''Participant ID'''
|'''UC1.1'''
|'''UC1.2'''
|'''UC1.3'''
|'''UC2.1'''
|'''UC2.2'''
|'''UC3.1'''
|'''UC3.2'''
|'''Notes'''
|-
|BMDW
|Bundesministerium fuer Digitalisierung und Wirtschaftsstandort
|AT
|iso6523-actorid-upis::9991:at000000271
|
|
|
|DE
DO
|DE

DO
|
|
|
|-
|BRZ
|Bundesrechenzentrum GMBH (Federal Data Center)
|AT
|
|
|
|
|DR
DT
|DR

DT
|
|
|BRZ has no Participant ID, because it is only DR and DT
|-
|SGAD
|Secretaría General de Administración Digital (General Secretariat for Digital Administration)
|ES
|iso6523-actorid-upis::9920:ess2833002e
|DR
DO,DT
|DO,DT
|DP
|
|
|DO,DT
|DE,DR
DO,DT
|Evidence in SA UCs is provided by the DE4A partner UJI.
|-
|UJI
|Universitat Jaume I de Castellón (Jaume I University of Castellón)
|ES
|iso6523-actorid-upis::9920:esq6250003h
|DE*
|
|
|
|
|
|
|*Connector provided by SGAD. UJI is also an evidence provider in all SA UCs through SGAD.
|-
|CTIE
|Centre des Technologies de l'Information de l'Etat (State Information Technology Center)
|LU
|iso6523-actorid-upis::9991:lu000000025
|
|
|
|
|
|DE,DR
DO,DT
|DE,DR
DO,DT
|
|-
|RVO
|Rijksdienst voor Ondernemend Nederland (Netherlands Enterprise Agency)
|NL
|iso6523-actorid-upis::9991:nl000000024
|
|
|
|DE,DR

DO,DT
|DE,DR

DO,DT
|
|
|
|-
|AMA-IP
|Agencia para a Modernizacao Administrativa IP (Administration Modernization Agency)
|PT
|iso6523-actorid-upis::9991:pt000000026
|DR
DT,DO
|DT
|
|
|
|DR
DO,DT
|DR
|AMA-IP consults INESC-ID in some cases when the latter takes the role of DO. Therefore, INESC-ID does not directly take part of the DE4A network as DO, but AMA-IP instead.
|-
|INESC-ID
|Institute for Systems and Computer Engineering, Technology and Science
|PT
|iso6523-actorid-upis::9991:pt990000101
|DE
|
|DC
DP
|
|
|
|
|
|-
|MoAI
|Ministerul Afacerilor Interne (Ministry of Internal Affairs)
|RO
|iso6523-actorid-upis::9991:ro000000005
|
|
|
|
|
|DE,DR

DO,DT
|DE,DR

DO,DT
|
|-
|ORNC
|Oficiul National B22 al Registrului Comertului
|RO
|iso6523-actorid-upis::9991:ro000000006
|
|
|
|DE,DR

DO,DT
|DE,DR

DO,DT
|
|
|
|-
|BVE
|Bolagsverket (Companies Registration Office)
|SE
|iso6523-actorid-upis::9991:se000000013
|
|
|
|DE,DR
|DE,DR
|
|
|
|-
|JSI
|Institut "Jožef Stefan" (Jožef Stefan Institute)
|SI
|iso6523-actorid-upis::9949:si55560822
|
|DE
|
|
|
|
|
|
|-
|MIZŠ
|Ministrstvo za izobraževanje, znanost in šport (Ministry of Education, Science and Sport)
|SI
|iso6523-actorid-upis::9949:si14246821
|DE
DO
|
|DC
DP
|
|
|
|
|*The central preview functionality for DO is provided by SI-MPA.
|-
|SI-MPA
|Ministrstvo za javno upravo (Ministry of Public Administration)
|SI
|iso6523-actorid-upis::9991:si000000015
|DR
DT
|DR
|
|
|
|DR,DT
|DR,DT
|
|-
|MNZ
|Ministrstvo za notranje zadeve (Ministry of the Interior)
|SI
|iso6523-actorid-upis::9949:si52817652
|
|
|
|
|
|DO
|DO
|*The central preview functionality for DO is provided by SI-MPA.
|}

=== Technical information on participants IT2 ===
{| class="wikitable"
!
==== Test domain (Playground) ====
!
==== Pilot domain ====
|-
|
{| class="wikitable"
! colspan="4" |SMP
|-
|'''Country'''
|'''Participant'''
|'''SMP endpoint'''
|'''SMP certificate'''
|-
|ES (shared)
|SGAD
|[https://de4a.redsara.es/sgad-smp https://de4a.redsara.es/sgad-smp/]
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD owncloud folder]
|}
|
{| class="wikitable"
! colspan="4" |SMP
|-
|'''Country'''
|'''Participant'''
|'''SMP endpoint'''
|'''SMP certificate'''
|-
|AT
|BRZ
|https://de4a-smp.usp.gv.at/
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD&fileid=1169370 owncloud folder]
|-
|ES
|SGAD
|
|
|-
|LU
|
|
|
|-
|NL
|
|
|
|-
|PT
|
|
|
|-
|RO
|
|
|
|-
|SE
|
|
|
|-
|SI
|SI-MPA
|https://toop-smp.pprod.medius.si/public
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SI-MPA owncloud folder]
|}
|-
|
{| class="wikitable"
! colspan="3" |DE
|-
|'''Participant'''
|'''Evidence types consumed'''
|'''DE e-procedure portal'''
|-
|BMDW
|Company Registration
|
|-
|SGAD
|Birth Evidence
Marriage Evidence
|
|-
|UJI
|Higher Education Diploma
|
|-
|CTIE
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|RVO
|Company Registration
|
|-
|INESC-ID
|Higher Education Diploma
Secondary Education Diploma
|
|-
|
|
|
|-
|MoAI
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|ORNC
|Company Registration
|
|-
|BVE
|Company Registration
|
|-
|JSI
|Higher Education Diploma
Large Family Evidence

Disability Evidence
|https://grants.e5.ijs.si/grants/public/
|-
|MIZŠ
|Higher Education Diploma
Secondary Education Diploma
|http://srvas2.rrc.si/prijava/?lang=en
|}
|
{| class="wikitable"
! colspan="3" |DE
|-
|'''Participant'''
|'''Evidence types consumed'''
|'''DE e-procedure portal'''
|-
|BMDW
|Company Registration
|
|-
|SGAD
|Birth Evidence
Marriage Evidence
|
|-
|UJI
|Higher Education Diploma
|
|-
|CTIE
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|RVO
|Company Registration
|
|-
|INESC-ID
|Higher Education Diploma
Secondary Education Diploma
|
|-
|
|
|
|-
|MoAI
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|ORNC
|Company Registration
|
|-
|BVE
|Company Registration
|
|-
|JSI
|Higher Education Diploma
Large Family Evidence

Disability Evidence
|
|-
|MIZŠ
|Higher Education Diploma
Secondary Education Diploma
|
|}
|-
|
{| class="wikitable"
! colspan="3" |DO
|-
|'''Participant'''
|'''Evidence types provided'''
|'''DO evidence portal'''
|-
|BMDW
|Company Registration
|
|-
|SGAD
|Higher Education Diploma
Secondary Education Diploma

Large Family Evidence

Disability Evidence

Domicile Registration Evidence

Birth Evidence

Marriage Evidence

Pension Evidence

Unemployment Evidence

Working Life Evidence
|
|-
|CTIE
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|RVO
|Company Registration
|
|-
|AMA-IP
|Domicile Registration Evidence
|
|-
|INESC-ID
|Higher Education Diploma
|
|-
|MoAI
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|ORNC
|Company Registration
|
|-
|MIZŠ
|Higher Education Diploma
|Direct public access is not enabled
|-
|MNZ
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|Direct public access is not enabled
|}
|
{| class="wikitable"
! colspan="3" |DO
|-
|'''Participant'''
|'''Evidence types provided'''
|'''DO evidence portal'''
|-
|BMDW
|Company Registration
|
|-
|SGAD
|Higher Education Diploma
Secondary Education Diploma

Large Family Evidence

Disability Evidence

Domicile Registration Evidence

Birth Evidence

Marriage Evidence

Pension Evidence

Unemployment Evidence

Working Life Evidence
|
|-
|CTIE
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|RVO
|Company Registration
|
|-
|AMA-IP
|Domicile Registration Evidence
|
|-
|INESC-ID
|Higher Education Diploma
|
|-
|MoAI
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|
|-
|ORNC
|Company Registration
|
|-
|MIZŠ
|Higher Education Diploma
|Direct public access is not enabled
|-
|MNZ
|Domicile Registration Evidence
Birth Evidence

Marriage Evidence
|Direct public access is not enabled
|}
|-
|
{| class="wikitable"
! colspan="3" |DR
|-
|'''Participant'''
|'''AS4 certificate'''
|'''Connector endpoint'''
|-
|BRZ
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD&fileid=1169370 owncloud folder]
|https://de4a.usp.gv.at/ado/phase4
|-
|SGAD
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD owncloud folder]
|https://pre-as4gw-dt-de4a.redsara.es/de4a-it2-connector/
|-
|CTIE
|
|
|-
|RVO
|
|
|-
|AMA-IP
|
|
|-
|ORNC
|
|
|-
|BVE
|
|
|-
|SI-MPA
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SI-MPA owncloud folder]
|https://toop-as4.pprod.medius.si/
|}
|
{| class="wikitable"
! colspan="3" |DR
|-
|'''Participant'''
|'''AS4 certificate'''
|'''Connector endpoint'''
|-
|SGAD
|
|
|-
|CTIE
|
|
|-
|RVO
|
|
|-
|AMA-IP
|
|
|-
|ORNC
|
|
|-
|BVE
|
|
|-
|SI-MPA
|
|
|}
|-
|
{| class="wikitable"
! colspan="3" |DT
|-
|'''Participant'''
|'''AS4 certificate'''
|'''Connector endpoint'''
|-
|BRZ
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD&fileid=1169370 owncloud folder]
|https://de4a.usp.gv.at/ado/phase4
|-
|SGAD
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SGAD owncloud folder]
|https://pre-as4gw-dt-de4a.redsara.es/de4a-it2-connector/
|-
|CTIE
|
|
|-
|RVO
|
|
|-
|AMA-IP
|
|
|-
|MoAI
|
|
|-
|ORNC
|
|
|-
|SI-MPA
|[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/Playground%20certificates/SI-MPA owncloud folder]
|https://toop-as4.pprod.medius.si/
|}
|
{| class="wikitable"
! colspan="3" |DT
|-
|'''Participant'''
|'''AS4 certificate'''
|'''Connector endpoint'''
|-
|BRZ
|
|
|-
|SGAD
|
|
|-
|CTIE
|
|
|-
|RVO
|
|
|-
|AMA-IP
|
|
|-
|MoAI
|
|
|-
|ORNC
|
|
|-
|SI-MPA
|
|
|}
|}

===DE-DO.json participant endpoint urls===
{| class="wikitable"
!
====Test domain (PRE2b) ====
!
====Pilot domain (PRO2)====
|-
|
{| class="wikitable"
! colspan="5" |Data Owners
|-
|'''Country'''
|'''Participant'''
|'''Participant ID'''
|'''Pattern'''
|'''DO Endpoint URL'''
|-
| rowspan="4" |AT
| rowspan="4" |
| rowspan="4" |iso6523-actorid-upis::99XX:at000000271-test-it2
|IM
|
|-
|USI
|
|-
| LU
|
|-
|SN
|
|-
| rowspan="4" | ES
| rowspan="4" |SGAD
| rowspan="4" |iso6523-actorid-upis::9920:ess2833002e-test-it2
|IM
|https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/requestExtractEvidenceIM
|-
|USI
|https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/do1/usi/extractevidence
|-
|LU
|https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/dataOwner/in/lu/
|-
|SN
|https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/dataOwner/in/sn/
|-
| rowspan="4" |PT
| rowspan="4" |AMA
| rowspan="4" | iso6523-actorid-upis::99XX:pt000000026-test-it2
|IM
|
|-
|USI
|
|-
| LU
|
|-
|SN
|
|-
| rowspan="4" |NL
| rowspan="4" |RVO
| rowspan="4" |iso6523-actorid-upis::99XX:nl000000024-test-it2
|IM
|
|-
|USI
|
|-
|LU
|
|-
|SN
|
|-
| rowspan="4" |SI
| rowspan="4" |MIZŠ
| rowspan="4" |iso6523-actorid-upis::9949:si14246821
|IM
|N/A
|-
|USI
|Not publicly disclosed
|-
|LU
|N/A
|-
|SN
|N/A
|-
|SI
|MNZ
|iso6523-actorid-upis::9949:si52817652
|USI
|Not publicly disclosed
|-
| rowspan="4" |SE
| rowspan="4" |BVE
| rowspan="4" |iso6523-actorid-upis::99XX:se000000013-test-it2
|IM
|
|-
|USI
|
|-
|LU
|
|-
|SN
|
|}
{| class="wikitable"
! colspan="5" |Data Evaluators
|-
|'''Country'''
|'''Participant'''
|'''Participant ID'''
|'''Response Type'''
|'''DE Endpoint URL'''
|-
| rowspan="4" | AT
| rowspan="4" |
| rowspan="4" |iso6523-actorid-upis::99XX:at000000271-test-it2
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" |ES
| rowspan="4" |SGAD
| rowspan="4" |iso6523-actorid-upis::9920:ess2833002e-test-it2
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" | ES
| rowspan="4" |UJI
| rowspan="4" |iso6523-actorid-upis::9920:esq6250003h-test-it2
|response
|
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |PT
| rowspan="4" | INESC-ID
| rowspan="4" |iso6523-actorid-upis::9991:pt990000101-test-it2
|response
|
|-
|subscription_resp
| N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |NL
| rowspan="4" |RVO
| rowspan="4" |iso6523-actorid-upis::99XX:nl000000024-test-it2
|response
|N/A
|-
|subscription_resp
| N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |MIZŠ
| rowspan="4" |iso6523-actorid-upis::9949:si14246821
|response
|http://srvas2.rrc.si/de4a/requestForwardEvidence
|-
|subscription_resp
|N/A
|-
|redirect
|http://srvas2.rrc.si/de4a/redirectUser
|-
|notification
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |JSI
| rowspan="4" |iso6523-actorid-upis::9949:si55560822-test-it2
| response
| https://grants.e5.ijs.si/grants/public/de-r/requestForwardEvidence
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |SE
| rowspan="4" |BVE
| rowspan="4" |iso6523-actorid-upis::99XX:se000000013-test-it2
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|}
|
{| class="wikitable"
! colspan="5" |Data Owners
|-
|'''Country'''
|'''Participant'''
|'''Participant ID'''
|'''Pattern'''
|'''DO Endpoint URL'''
|-
| rowspan="4" |AT
| rowspan="4" |
| rowspan="4" |
|IM
|N/A
|-
|USI
|N/A
|-
| LU
|N/A
|-
|SN
|N/A
|-
| rowspan="4" | ES
| rowspan="4" |SGAD
| rowspan="4" |
|IM
|N/A
|-
|USI
|N/A
|-
|LU
|N/A
|-
|SN
|N/A
|-
| rowspan="4" |PT
| rowspan="4" |AMA
| rowspan="4" |
|IM
| N/A
|-
|USI
|N/A
|-
| LU
| N/A
|-
|SN
|N/A
|-
| rowspan="4" |NL
| rowspan="4" |RVO
| rowspan="4" |
|IM
|N/A
|-
|USI
|N/A
|-
|LU
|N/A
|-
|SN
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |MIZŠ
| rowspan="4" |iso6523-actorid-upis::9949:si14246821
|IM
|N/A
|-
|USI
|Not publicly disclosed
|-
|LU
|N/A
|-
|SN
|N/A
|-
|SI
|MNZ
|iso6523-actorid-upis::9949:si52817652
|USI
|Not publicly disclosed
|-
| rowspan="4" |SE
| rowspan="4" |BVE
| rowspan="4" |
|IM
|N/A
|-
|USI
|N/A
|-
|LU
|N/A
|-
|SN
|N/A
|}
{| class="wikitable"
! colspan="5" |Data Evaluators
|-
|'''Country'''
|'''Participant'''
|'''Participant ID'''
|'''Response Type'''
|'''DE Endpoint URL'''
|-
| rowspan="4" | AT
| rowspan="4" |
| rowspan="4" |
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" |ES
| rowspan="4" |SGAD
| rowspan="4" |
|response
|N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" | ES
| rowspan="4" |UJI
| rowspan="4" |
|response
|
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |PT
| rowspan="4" | INESC-ID
| rowspan="4" |
|response
|
|-
|subscription_resp
| N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |NL
| rowspan="4" |RVO
| rowspan="4" |
|response
|N/A
|-
|subscription_resp
| N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |MIZŠ
| rowspan="4" |iso6523-actorid-upis::9949:si14246821
|response
|
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |SI
| rowspan="4" |JSI
| rowspan="4" |iso6523-actorid-upis::9949:si55560822
| response
|
|-
|subscription_resp
|N/A
|-
|redirect
|
|-
|notification
|N/A
|-
| rowspan="4" |SE
| rowspan="4" |BVE
| rowspan="4" |
|response
| N/A
|-
|subscription_resp
|N/A
|-
|redirect
|N/A
|-
|notification
|N/A
|}

|}

==DE4A infrastructure IT2==
===Playground infrastructure IT2===
The following diagram depicts the Playground infrastructure for the second iteration, with the deployment of its corresponding components.[[File:DE4A network IT2-Playground IT2.drawio.png|frame|alt=|none]]

===Pilot partners infrastructure flavours IT2 ===
The following two diagrams outline the general infrastructure expected from the Member States and partners involved in the pilots. Each Connector is in turn connected and exchanges data with the corresponding Connector (DR or DT) of the Playground or other partners.

At this stage, all DE4A participants are expected to follow the set-up A, while only Romania is expected to follow set-up B.[[File:DE4A network IT2-Country set-up A.drawio.png|frame|alt=|left]]

[[File:DE4A network IT2-Country set-up B.drawio.png|frame|alt=|none]]

== Domains and types of participant IDs ==

===DE4A domains===
In DE4A, there are two types of participants:

*Imaginary participants: intended to query the examples stored in the Mocked DO.
*Real participants: intended to retrieve data directly returned by partners.

At the same time, for the real participants, there are also two “domains”:

*Test domain: only fake data is used for test purposes. It is the domain related to the DE4A Playground, where participants return datasets from test sources.
*Pilot domain: real data from real citizens and companies is supposed to be used. It is the environment used for the running phase of the pilots, where participants access to their real registries and return real evidence from them.

Finally, the project is divided into two iterations where each of them needs a copy of those two domains, and where some overlap between them occurs.
[[File:Domain overlap.png|none|thumb|910x910px]]
As the DE4A project uses the dynamic discovery of eDelivery, where there cannot be duplicate participant IDs targeting to different Connectors (depending on the domain concerned), we need to define a different participant ID schema per each domain:

*'''PRE1a''': Imaginary participants stored in the Mocked DO for iteration 1 for testing. The related evidence is stored in the Mocked DO deployed in SGAD (ES).
** Scheme identifier used: “'''9999'''”.
** Suffix used: “'''-it1'''”.
**E.g. iso6523-actorid-upis::99'''99''':ess2833002e'''-it1'''

*'''PRE1b:''' Simulated data returned by the real participants used for testing in Playground iteration 1. The related evidence is located in each partner’s infrastructure, within their test domain.
**Scheme identifier used: “'''99XX'''”, where “XX” depends on the identifier each participant is using.
**Suffix used: “'''-it1'''”.
**E.g. iso6523-actorid-upis::99'''20''':ess2833002e'''-it1'''
*'''PRO1:''' Real data returned by the real participants during the execution of phase 1 of the pilot. The related evidence is located in each partner’s infrastructure, within their pilot domain.
**Scheme identifier used: “'''99XX'''”, where “XX” depends on the identifier each participant is using. It is the “real” participant ID.
**Suffix used: ''none'', since there is no overlap between phases 1 and 2 of the pilots.
**E.g. iso6523-actorid-upis::99'''20''':ess2833002e
*'''PRE2a:''' Imaginary participants stored in the Mocked DO for iteration 2 for testing. The related evidence is stored in the Mocked DO deployed in SGAD (ES).
**Scheme identifier used: “'''9999'''”.
**Suffix used: “'''-mock-it2'''”.
**E.g. iso6523-actorid-upis::99'''99''':ess2833002e'''-mock-it2'''
*'''PRE2b:''' Simulated data returned by the real participants used for testing in Playground iteration 2. The related evidence is located in each partner’s infrastructure, within their test domain.
**Scheme identifier used: “'''99XX'''”, where “XX” depends on the identifier each participant is using.
**Suffix used: “'''-test-it2'''”.
**E.g. iso6523-actorid-upis::99'''20''':ess2833002e'''-test-it2'''
*'''PRO2:''' Real data returned by the real participants during the execution of phase 2 of the pilot. The related evidence is located in each partner’s infrastructure, within their pilot domain.
**Scheme identifier used: “'''99XX'''”, where “XX” depends on the identifier each participant is using. It is the “real” participant ID.
**Suffix used: ''none'', since there is no overlap between phases 1 and 2 of the pilots.
**E.g. iso6523-actorid-upis::99'''20''':ess2833002e

Therefore, DE4A domains are differentiated by the participant ID schema used.

===Location of the participant IDs===
These different participant IDs must be stored in their corresponding IDKs and SMPs and configured to return the proper information:

*'''PRE1a:''' Imaginary participants
**IDK: none (for these participants, the mocked DE knows which the imaginary participants are and which DO to query, namely, the mocked DO of the first iteration).
**SMP: shared SMP of the Playground IT1. It returns the routing information of the targeted Connector (DR/DT) of the Playground IT1.
*'''PRE1b''': Simulated data from real participants
**IDK: mocked IDK of the Playground IT1.
**SMP: shared SMP of the Playground IT1. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.
*'''PRO1:''' Real data from real participants
**IDK: mocked IDK of the pilot running environment.
**SMP: national SMP of the requested participant. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.
***For the first pilot running phase, partners who have not yet deployed their own SMPs will be able to use a shared SMP provided by one of the partners with an available SMP. In such cases, the routing information of those partners will be stored in this shared SMP.
*'''PRE2a:''' Imaginary participants
**IDK: Central IAL. Its information is automatically updated and fed from the SMPs connected to it.
**SMP: shared SMP of the Playground IT2. It returns the routing information of the targeted Connector (DR/DT) of the Playground IT2.
*'''PRE2b:''' Simulated data from real participants
**IDK: Central IAL. Its information is automatically updated and fed from the SMPs connected to it.
**SMP: national SMP of the requested participant. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.
*'''PRO2:''' Real data from real participants
**IDK: Central IAL. Its information is automatically updated and fed from the SMPs connected to it.
**SMP: national SMP of the requested participant. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.