DE4A Playground it2 - Revision history

Javier.ferrero at 10:51, 22 March 2023

2023-03-22T10:51:04Z

Mpttfp eduardo.moreno at 08:28, 22 March 2023

2023-03-22T08:28:04Z

Hugo.berdon: /* User interface */

2022-11-10T12:02:31Z

User interface

Hugo.berdon: /* Data Requestor */

2022-11-10T11:57:05Z

Data Requestor

Hugo.berdon: /* Data used */

2022-11-10T11:55:39Z

Data used

Hugo.berdon: /* Data Owner (MOCK-DO) */

2022-11-10T11:51:47Z

Data Owner (MOCK-DO)

Hugo.berdon at 11:50, 10 November 2022

2022-11-10T11:50:46Z

Hugo.berdon: /* Data Owner */

2022-11-10T11:49:02Z

Data Owner

Hugo.berdon: /* IAL Directory */

2022-11-10T11:44:14Z

IAL Directory

Hugo.berdon: /* Mocked IDK */

2022-11-10T11:21:07Z

Mocked IDK

@@ Line 9: / Line 9: @@
 [[File:DE4A network IT2 v2-Playground IT2.png|none|thumb|743x743px]]
 == Supported interaction patterns ==
 The Data Evaluator was designed to simulate all the iteraction patterns available. For more information [[Common behaviour and interactions between components]]

← Older revision		Revision as of 08:28, 22 March 2023
Line 9:		Line 9:

	[[File:DE4A network IT2 v2-Playground IT2.png\|none\|thumb\|743x743px]]		[[File:DE4A network IT2 v2-Playground IT2.png\|none\|thumb\|743x743px]]
		+	[[File:DE4A network IT2-Playground IT2.drawio.png\|none\|thumb\|743x743px]]

	== Supported interaction patterns ==		== Supported interaction patterns ==

@@ Line 178: / Line 178: @@
 For the DO the outbound connection are HTTP POST of ''ResponseUserRedirection'' data structures to the URL supplied by the DE in the ''RequestUserRedirection'' HTTP POST and if configured to send logs to the Kafka server, either directly via TCP or using the HTTP proxy.
-==== User interface ====
+=== User interface ===
 == Data Requestor ==

@@ Line 75: / Line 75: @@
 '''Note''': the terminology used in the demo application is very simplified and may not suffice the needs of real-world applications. Real pilot applications should align the texts with their local needs.
-==== System requirements ====
+==== Technology used ====
 The DE4A WP5 Demo UI is a web application. The user interface is based on the Bootstrap 4.6 framework and the system requirements for using it are documented at https://getbootstrap.com/docs/4.6/getting-started/browsers-devices/
@@ Line 129: / Line 129: @@
 Its codebase can be found at https://github.com/de4a-wp5/de4a-connector-mock and the related deployed instance at https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/do1/preview/index
 ==== Technology used ====
@@ Line 179: / Line 177: @@
 The mocked DO is running over an Apache Tomcat 9 server located at: https://pre-smp-dr-de4a.redsara.es/de4a-mock-connector/
 For the DO the outbound connection are HTTP POST of ''ResponseUserRedirection'' data structures to the URL supplied by the DE in the ''RequestUserRedirection'' HTTP POST and if configured to send logs to the Kafka server, either directly via TCP or using the HTTP proxy.
 == Data Requestor ==

@@ Line 79: / Line 79: @@
 The backend was deployed with Java11 and Spring Framework. And is deployed on an Apache Tomcat 9.
 ==== User interface ====
@@ Line 138: / Line 141: @@
 === Deployment and configuration ===
 The mocked DO functionality is performed by an instance of the de4a-connector-mock project [7]. The application allows to configure different parameters related to each role that the mock could assume. In this case, the DO related ones will be listed:

@@ Line 64: / Line 64: @@
 The DO and the DT are deployed at SGAD (ES). All other components, including the [[Usage of third party specifications and components|Kafka]] Server, are deployed at SGAD subcontractor facilities (ES).
-=== Data Evaluator (DEMO-UI) ===
+== Data Evaluator (DEMO-UI) ==
 The Data Evaluator deployed in the Playground was developed as a separate piece of software.

@@ Line 27: / Line 27: @@
 ===== Intermediation IM Pattern - Backwards compatibility =====
 It provides compatibility message exchange towards iteration 1 Data Owners, so it is possible to send request from it2 Data Evaluators to it1 Data Owners.
 == Uses of Playground ==
@@ Line 64: / Line 52: @@
 For the SMP CA we needed to use a CA that matches the requirements of CEF, as the maintainers of the Service Metadata Locator (SML). To fulfil our urgent needs for a suitable CA, CEF was kind to offer us 10 SMP certificates based on their trusted “Connectivity Test CA”. In parallel to that, we promised CEF to search a commercial CA that we could use as a sustainable solution for SMP certificates. The requirements are outlined in the “Trust Models Guidance” document of CEF.
-== Data Evaluator (DEMO-UI) ==
+== Playground components ==
 The Data Evaluator deployed in the Playground was developed as a separate piece of software.

@@ Line 10: / Line 10: @@
 [[File:DE4A network IT2 v2-Playground IT2.png|none|thumb|743x743px]]
-== Playground components ==
+== Supported interaction patterns ==
 The Data Evaluator was designed to simulate all the iteraction patterns available. For more information [[Common behaviour and interactions between components]]
@@ Line 51: / Line 27: @@
 ===== Intermediation IM Pattern - Backwards compatibility =====
 It provides compatibility message exchange towards iteration 1 Data Owners, so it is possible to send request from it2 Data Evaluators to it1 Data Owners.
 == Uses of Playground ==
@@ Line 76: / Line 64: @@
 For the SMP CA we needed to use a CA that matches the requirements of CEF, as the maintainers of the Service Metadata Locator (SML). To fulfil our urgent needs for a suitable CA, CEF was kind to offer us 10 SMP certificates based on their trusted “Connectivity Test CA”. In parallel to that, we promised CEF to search a commercial CA that we could use as a sustainable solution for SMP certificates. The requirements are outlined in the “Trust Models Guidance” document of CEF.
-== Data Evaluator ==
+== Data Evaluator (DEMO-UI) ==
 The Data Evaluator deployed in the Playground was developed as a separate piece of software.
@@ Line 135: / Line 120: @@
 [[File:USI Exchange (Expert mode) .png|none|thumb|781x781px]]
-== Data Owner ==
+== Data Owner (MOCK-DO) ==
-The Playground DO is deployed with example evidences that it can receive queries for. These are example identifiers from multiple different DOs. For the USI pattern the mocked DO provides a preview functionality, where the user has to consent to sending the evidence before it is sent back to the DE. Together with the DE it provides the user interfaces making the full user journey possible.
+The test Data Owner is deployed as a standalone software component. If provides test evidence based on example IDs of different DOs.
 [[File:Demoui-user-ui-10.png|alt=The DO preview page|none|thumb|579x579px|The DO preview page]]

@@ Line 242: / Line 242: @@
 == IAL Directory ==
-Testing component used to simulate the Information Desk behaviour and provide APIs to the Playground based on the [https://wiki.de4a.eu/index.php/Information_Desk IDK definition by WP3]. This mocked component comes from the necessity of the a IDK funcionality and the lack of developments around this centraliced component. Therefore WP5 mocked the funcionality to be used in the playground of the iteration 1 and 2.
+Issuing Authority Locator (IAL) component helps Data Consumers (DC) to find out the issuing authority within a particular country either to obtain a canonical evidence type or to subscribe a canonical event catalogue, and know the characteristics of the evidence provision or the subscription provision, respectively.
-To have a more realistic scenario around the Connector, a mocked IDK component has been developed to simulate the data exchanged with the component. It is just a web application that stores information about the data providers (DOs) of each evidence and country, modelled on tables. It also provides the corresponding interfaces to consume that information by an external component, following the current functional and technical definition of the IDK.
+For more information, [[DE4A Issuing Authority Locator (IAL)]]
 == eDelivery ==
@@ Line 328: / Line 309: @@
 ** Dynamic discovery mode.
 ** DE4A SML configured.
 == Kafka server ==

@@ Line 241: / Line 241: @@
 </pre>All messages sent by the Kafka Client will be viewable by anyone going to the Package Tracker URL https://de4a.simplegob.com/package-tracker/#!detail.
-== Mocked IDK ==
+== IAL Directory ==
 Testing component used to simulate the Information Desk behaviour and provide APIs to the Playground based on the [https://wiki.de4a.eu/index.php/Information_Desk IDK definition by WP3]. This mocked component comes from the necessity of the a IDK funcionality and the lack of developments around this centraliced component. Therefore WP5 mocked the funcionality to be used in the playground of the iteration 1 and 2.