SA UC1 Components - Revision history

Tomaz.klobujar: /* Common OOP TS components */

2022-01-24T12:17:19Z

Common OOP TS components

Tomaz.klobujar: /* Common eIDAS components */

2021-05-06T13:14:55Z

Common eIDAS components

Tomaz.klobujar: /* Common OOP TS components */

2021-05-06T13:07:18Z

Common OOP TS components

Tomaz.klobujar: /* Common OOP TS components */

2021-05-06T13:06:25Z

Common OOP TS components

Tomaz.klobujar: /* Common OOP TS components */

2021-05-06T13:03:31Z

Common OOP TS components

Tomaz.klobujar at 10:27, 6 May 2021

2021-05-06T10:27:16Z

Tomaz.klobujar: Created page with "SA UC1 Components"

2021-05-06T10:02:35Z

Created page with "SA UC1 Components"

New page

SA UC1 Components

@@ Line 37: / Line 37: @@
 DNS entries will be created from the registration of SMPs: the  SML, which is also centrally hosted by CEF.
 |-
 |[[DE4A Connector]]
 |Data requestor and data  transferor
-|The DE4A connector is  the reference software that data requestors and data transferors can use to  connect to the DE4A OOP TS. This eases the work by abstracting the  communication with the components. The DE4A Connector already includes the  Phase4 AS4 gateway for the Member States that do not want to have a separate  gateway.
+|The DE4A connector is  the reference software that data requestors and data transferors can use to  connect to the DE4A OOP TS. This eases the work by abstracting the  communication with the components. The DE4A Connector already includes the  Phase4 AS4 gateway.
 |}

← Older revision		Revision as of 13:14, 6 May 2021
Line 2:		Line 2:

	== Common eIDAS components ==		== Common eIDAS components ==
		+	{\| class="wikitable"
		+	\|'''Component'''
		+	\|'''Role'''
		+	\|'''Short description of its use'''
		+	\|-
		+	\|eIDAS connector
		+	\|Authentication connector
		+	\|The component Member States implement to connect to the eIDAS network as a relying party. The connector accepts authentication requests from the service providers of the Member State and forwards the requests to the Member States that needs to authenticate the user. After authentication, the eIDAS connector receives the authentication results and sends them to the requesting service provider (relying party).
		+	\|-
		+	\|eIDAS proxy
		+	\|Authentication proxy
		+	\|The component Member States implement to allow authentication with their (notified) eID for services provided in other Member States. The eIDAS proxy receives authentication requests from relying Member States and coordinates authentication. The eIDAS proxy then sends the result to the requesting eIDAS connector.
		+	\|}

	== Common OOP TS components ==		== Common OOP TS components ==

@@ Line 9: / Line 9: @@
 |'''Short description of its use'''
 |-
-|Information Desk  configuration file
+|[[Information Desk]] configuration file
 |Data requestor and data  transferor
 |The diploma issuing  authorities can be located at a national level (Slovenia, Spain) or  university level (Portugal). The information will be stored in a  configuration file in the DE4A connector for MVP.

@@ Line 13: / Line 13: @@
 |The diploma issuing  authorities can be located at a national level (Slovenia, Spain) or  university level (Portugal). The information will be stored in a  configuration file in the DE4A connector for MVP.
 |-
-|SMP
+|[[SMP]]
 |Data requestor and data transferor
@@ Line 19: / Line 19: @@
 |For each evidence request and response, information on the  receivers Access Point (URL) and its certificates are needed. It is expected  there will a common project SMP for the test phase, while each Member State  will host an SMP for the close-to-production phase. Before sending a request  or response, the sending party queries the SMP of the receiver to get this  info.
 |-
-|DNS & SML
+|[[DNS]] & [[SML]]
 |Data requestor and data transferor
 |As there are multiple SMPs, the sending  party needs to know where to find the SMP of the receiver to get the actual  metadata. This location can be found in the centrally CEF-hosted DNS, that  will be queried by the access point of the sending Member State.
@@ Line 29: / Line 29: @@
 |This component – also referred to as eDelivery  access point – handles the secure transfer of the data, including encryption  and decryption as well as signing/sealing payloads and validating  signatures/seals.
 |-
-|DE4A Connector
+|[[DE4A Connector]]
 |Data requestor and data  transferor
 |The DE4A connector is  the reference software that data requestors and data transferors can use to  connect to the DE4A OOP TS. This eases the work by abstracting the  communication with the components. The DE4A Connector already includes the  Phase4 AS4 gateway for the Member States that do not want to have a separate  gateway.
 |}

← Older revision		Revision as of 13:03, 6 May 2021
Line 4:		Line 4:

	== Common OOP TS components ==		== Common OOP TS components ==
		+	{\| class="wikitable"
		+	\|'''Component'''
		+	\|'''Role'''
		+	\|'''Short description of its use'''
		+	\|-
		+	\|Information Desk configuration file
		+	\|Data requestor and data transferor
		+	\|The diploma issuing authorities can be located at a national level (Slovenia, Spain) or university level (Portugal). The information will be stored in a configuration file in the DE4A connector for MVP.
		+	\|-
		+	\|SMP
		+	\|Data requestor and data transferor
		+
		+	/ central
		+	\|For each evidence request and response, information on the receivers Access Point (URL) and its certificates are needed. It is expected there will a common project SMP for the test phase, while each Member State will host an SMP for the close-to-production phase. Before sending a request or response, the sending party queries the SMP of the receiver to get this info.
		+	\|-
		+	\|DNS & SML
		+	\|Data requestor and data transferor
		+	\|As there are multiple SMPs, the sending party needs to know where to find the SMP of the receiver to get the actual metadata. This location can be found in the centrally CEF-hosted DNS, that will be queried by the access point of the sending Member State.
		+
		+	DNS entries will be created from the registration of SMPs: the SML, which is also centrally hosted by CEF.
		+	\|-
		+	\|eDelivery AS4 gateway
		+	\|Data requestor and data transferor
		+	\|This component – also referred to as eDelivery access point – handles the secure transfer of the data, including encryption and decryption as well as signing/sealing payloads and validating signatures/seals.
		+	\|-
		+	\|DE4A Connector
		+	\|Data requestor and data transferor
		+	\|The DE4A connector is the reference software that data requestors and data transferors can use to connect to the DE4A OOP TS. This eases the work by abstracting the communication with the components. The DE4A Connector already includes the Phase4 AS4 gateway for the Member States that do not want to have a separate gateway.
		+	\|}

← Older revision		Revision as of 10:27, 6 May 2021
Line 1:		Line 1:
−	SA UC1 ~~Components~~	+	''Back to [[Use_Case_"Application_to_Public_Higher_Education"_(SA_UC1)\|main SA UC1 page]]''
		+
		+	== Common eIDAS components ==
		+
		+	== Common OOP TS components ==