SA UC3 Process - Revision history

Tomaz.klobujar at 12:54, 5 July 2021

2021-07-05T12:54:36Z

Tomaz.klobujar at 12:54, 5 July 2021

2021-07-05T12:54:04Z

Martina.sestak at 12:23, 29 June 2021

2021-06-29T12:23:57Z

Martina.sestak at 12:21, 29 June 2021

2021-06-29T12:21:01Z

Tomaz.klobujar: Created page with "Description of the SA UC3 process"

2021-05-06T13:38:14Z

Created page with "Description of the SA UC3 process"

New page

Description of the SA UC3 process

@@ Line 1: / Line 1: @@
 In MVP 1.0, the UC3 process flow includes the following steps:
-*''Obtaining of a Verifiable Credential''
+*''Obtaining a Verifiable Credential''
 **A student accesses an [https://wiki.de4a.eu/index.php/Evidence_Portal Evidence Portal] of a Data Provider (DP) to obtain a Verifiable Credential (VC).
 **The student is asked to authenticate at the DP using a legally recognized electronic identity (eIDAS identity).

@@ Line 1: / Line 1: @@
 In MVP 1.0, the UC3 process flow includes the following steps:
-*A student accesses an [https://wiki.de4a.eu/index.php/Evidence_Portal Evidence Portal] of a Data Provider (DP) to obtain a Verifiable Credential (VC).
+*''Obtaining of a Verifiable Credential''
-*The student is asked to authenticate at the DP using a legally recognized electronic identity (eIDAS identity).
+**A student accesses an [https://wiki.de4a.eu/index.php/Evidence_Portal Evidence Portal] of a Data Provider (DP) to obtain a Verifiable Credential (VC).
-*After successful authentication, the student explicitly requests that he/she wants to obtain diploma evidence from the DP in the form of a Verifiable Credential.
+**The student is asked to authenticate at the DP using a legally recognized electronic identity (eIDAS identity).
-*If the DID connection between the student's [https://wiki.de4a.eu/index.php/User_Agent User Agent] (mobile wallet) and the [https://wiki.de4a.eu/index.php/Authority_Agent Authority Agent] integrated into the [https://wiki.de4a.eu/index.php/Evidence_Portal Evidence Portal] has not yet been established, he/she requests a new QR code to be generated in order to establish the DID connection between two agents.
+**After successful authentication, the student explicitly requests that he/she wants to obtain diploma evidence from the DP in the form of a Verifiable Credential.
-*The student scans the QR code displayed in the [https://wiki.de4a.eu/index.php/Evidence_Portal Evidence Portal] in his mobile wallet application and accepts the DID connection invitation.
+**If the DID connection between the student's [https://wiki.de4a.eu/index.php/User_Agent User Agent] (mobile wallet) and the [https://wiki.de4a.eu/index.php/Authority_Agent Authority Agent] integrated into the [https://wiki.de4a.eu/index.php/Evidence_Portal Evidence Portal] has not yet been established, he/she requests a new QR code to be generated in order to establish the DID connection between two agents.
-*Once the DID connection is established, the student requests the DP to send him his/her diploma evidence as a Verifiable Credential to his mobile wallet.
+**The student scans the QR code displayed in the [https://wiki.de4a.eu/index.php/Evidence_Portal Evidence Portal] in his mobile wallet application and accepts the DID connection invitation.
-*The DP retrieves the student's diploma from a registry, transforms it into a canonical format according to the [https://wiki.de4a.eu/index.php/SA_UC3_Data_Model UC3 data model] and to the JSON-LD format of a Verifiable Credential, digitally signs it with its DID key and sends it for preview on the student's mobile phone.
+**Once the DID connection is established, the student requests the DP to send him his/her diploma evidence as a Verifiable Credential to his mobile wallet.
-*The student previews the Verifiable Credential offered by the DP and accepts the DP's VC offer.
+**The DP retrieves the student's diploma from a registry, transforms it into a canonical format according to the [https://wiki.de4a.eu/index.php/SA_UC3_Data_Model UC3 data model] and to the JSON-LD format of a Verifiable Credential, digitally signs it with its DID key and sends it for preview on the student's mobile phone.
-*The DP sends the final Verifiable Credential to the student who accepts the received VC and stores it under an arbitrary name in his/her mobile wallet for any future use.
+**The student previews the Verifiable Credential offered by the DP and accepts the DP's VC offer.
-*A student then accesses an [https://wiki.de4a.eu/index.php/EProcedure_Portal eProcedure Portal] of a Data Consumer (DC) to submit a Verifiable Presentation (VP) for the required procedure.
+**The DP sends the final Verifiable Credential to the student who accepts the received VC and stores it under an arbitrary name in his/her mobile wallet for any future use.
-*The student is asked to authenticate at the DC using a legally recognized electronic identity (eIDAS identity).
+*''Presenting a Verifiable Presentation''
-*After successful authentication, the student explicitly requests that he/she wants to submit diploma evidence to the DC in the form of a Verifiable Presentation.
+**A student then accesses an [https://wiki.de4a.eu/index.php/EProcedure_Portal eProcedure Portal] of a Data Consumer (DC) to submit a Verifiable Presentation (VP) for the required procedure.
-*If the DID connection between the student's [https://wiki.de4a.eu/index.php/User_Agent User Agent] (mobile wallet) and the [https://wiki.de4a.eu/index.php/Authority_Agent Authority Agent] integrated into the [https://wiki.de4a.eu/index.php/EProcedure_Portal eProcedure Portal] the has not yet been established, he/she requests a new QR code to be generated in order to establish the DID connection between two agents.
+**The student is asked to authenticate at the DC using a legally recognized electronic identity (eIDAS identity).
-*The student scans the QR code displayed in the [https://wiki.de4a.eu/index.php/EProcedure_Portal eProcedure Portal] in his mobile wallet application and accepts the DID connection invitation.
+**After successful authentication, the student explicitly requests that he/she wants to submit diploma evidence to the DC in the form of a Verifiable Presentation.
-*Once the DID connection is established, the student requests the DC to send him his/her a request for a VP submission.
+**If the DID connection between the student's [https://wiki.de4a.eu/index.php/User_Agent User Agent] (mobile wallet) and the [https://wiki.de4a.eu/index.php/Authority_Agent Authority Agent] integrated into the [https://wiki.de4a.eu/index.php/EProcedure_Portal eProcedure Portal] the has not yet been established, he/she requests a new QR code to be generated in order to establish the DID connection between two agents.
-*The DC sends a request to the student containing information on the expected VP format to be submitted for procedural requirements.
+**The student scans the QR code displayed in the [https://wiki.de4a.eu/index.php/EProcedure_Portal eProcedure Portal] in his mobile wallet application and accepts the DID connection invitation.
-*The student accepts the received request on his/her mobile phone by selecting the requested VP conforming to the request format from his/her mobile wallet and submitting it as a response to the DC's request.
+**Once the DID connection is established, the student requests the DC to send him his/her a request for a VP submission.
-*The DC receives and stores the VP submitted by the student under a specific name for any future references.
+**The DC sends a request to the student containing information on the expected VP format to be submitted for procedural requirements.
-*The student explicitly requests the DC to validate the submitted VP.
+**The student accepts the received request on his/her mobile phone by selecting the requested VP conforming to the request format from his/her mobile wallet and submitting it as a response to the DC's request.
-*The [https://wiki.de4a.eu/index.php/Authority_Agent Authority Agent] integrated into the [https://wiki.de4a.eu/index.php/EProcedure_Portal eProcedure Portal] validates the submitted VP in terms of the VC issuer (DP), holder (student) and the VC schema, and displays validation results. During the validation, the [https://wiki.de4a.eu/index.php/Authority_Agent Authority Agent] uses the integrated EBSI/eSSIF Connector to check the VP against entries in the EBSI registries (TIR, TSR).
+**The DC receives and stores the VP submitted by the student under a specific name for any future references.

@@ Line 1: / Line 1: @@
 In MVP 1.0, the UC3 process flow includes the following steps:
-*A student accesses an [https://wiki.de4a.eu/index.php/Evidence_Portal] of a Data Provider (DP) to obtain a Verifiable Credential (VC).
+*A student accesses an [https://wiki.de4a.eu/index.php/Evidence_Portal Evidence Portal] of a Data Provider (DP) to obtain a Verifiable Credential (VC).
 *The student is asked to authenticate at the DP using a legally recognized electronic identity (eIDAS identity).
 *After successful authentication, the student explicitly requests that he/she wants to obtain diploma evidence from the DP in the form of a Verifiable Credential.
-*If the DID connection between the student's [https://wiki.de4a.eu/index.php/User_Agent] (mobile wallet) and the [https://wiki.de4a.eu/index.php/Authority_Agent] integrated into the [https://wiki.de4a.eu/index.php/Evidence_Portal] has not yet been established, he/she requests a new QR code to be generated in order to establish the DID connection between two agents.
+*If the DID connection between the student's [https://wiki.de4a.eu/index.php/User_Agent User Agent] (mobile wallet) and the [https://wiki.de4a.eu/index.php/Authority_Agent Authority Agent] integrated into the [https://wiki.de4a.eu/index.php/Evidence_Portal Evidence Portal] has not yet been established, he/she requests a new QR code to be generated in order to establish the DID connection between two agents.
-*The student scans the QR code displayed in the [https://wiki.de4a.eu/index.php/Evidence_Portal] in his mobile wallet application and accepts the DID connection invitation.
+*The student scans the QR code displayed in the [https://wiki.de4a.eu/index.php/Evidence_Portal Evidence Portal] in his mobile wallet application and accepts the DID connection invitation.
 *Once the DID connection is established, the student requests the DP to send him his/her diploma evidence as a Verifiable Credential to his mobile wallet.
-*The DP retrieves the student's diploma from a registry, transforms it into a canonical format according to the [https://wiki.de4a.eu/index.php/SA_UC3_Data_Model] and to the JSON-LD format of a Verifiable Credential, digitally signs it with its DID key and sends it for preview on the student's mobile phone.
+*The DP retrieves the student's diploma from a registry, transforms it into a canonical format according to the [https://wiki.de4a.eu/index.php/SA_UC3_Data_Model UC3 data model] and to the JSON-LD format of a Verifiable Credential, digitally signs it with its DID key and sends it for preview on the student's mobile phone.
 *The student previews the Verifiable Credential offered by the DP and accepts the DP's VC offer.
 *The DP sends the final Verifiable Credential to the student who accepts the received VC and stores it under an arbitrary name in his/her mobile wallet for any future use.
-*A student then accesses an [https://wiki.de4a.eu/index.php/EProcedure_Portal] of a Data Consumer (DC) to submit a Verifiable Presentation (VP) for the required procedure.
+*A student then accesses an [https://wiki.de4a.eu/index.php/EProcedure_Portal eProcedure Portal] of a Data Consumer (DC) to submit a Verifiable Presentation (VP) for the required procedure.
 *The student is asked to authenticate at the DC using a legally recognized electronic identity (eIDAS identity).
 *After successful authentication, the student explicitly requests that he/she wants to submit diploma evidence to the DC in the form of a Verifiable Presentation.
-*If the DID connection between the student's [https://wiki.de4a.eu/index.php/User_Agent] (mobile wallet) and the [https://wiki.de4a.eu/index.php/Authority_Agent] integrated into the [https://wiki.de4a.eu/index.php/EProcedure_Portal] the has not yet been established, he/she requests a new QR code to be generated in order to establish the DID connection between two agents.
+*If the DID connection between the student's [https://wiki.de4a.eu/index.php/User_Agent User Agent] (mobile wallet) and the [https://wiki.de4a.eu/index.php/Authority_Agent Authority Agent] integrated into the [https://wiki.de4a.eu/index.php/EProcedure_Portal eProcedure Portal] the has not yet been established, he/she requests a new QR code to be generated in order to establish the DID connection between two agents.
-*The student scans the QR code displayed in the [https://wiki.de4a.eu/index.php/EProcedure_Portal] in his mobile wallet application and accepts the DID connection invitation.
+*The student scans the QR code displayed in the [https://wiki.de4a.eu/index.php/EProcedure_Portal eProcedure Portal] in his mobile wallet application and accepts the DID connection invitation.
 *Once the DID connection is established, the student requests the DC to send him his/her a request for a VP submission.
 *The DC sends a request to the student containing information on the expected VP format to be submitted for procedural requirements.
@@ Line 19: / Line 19: @@
 *The DC receives and stores the VP submitted by the student under a specific name for any future references.
 *The student explicitly requests the DC to validate the submitted VP.
-*The [https://wiki.de4a.eu/index.php/Authority_Agent] integrated into the [https://wiki.de4a.eu/index.php/EProcedure_Portal] validates the submitted VP in terms of the VC issuer (DP), holder (student) and the VC schema, and displays validation results. During the validation, the [https://wiki.de4a.eu/index.php/Authority_Agent] uses the integrated EBSI/eSSIF Connector to check the VP against entries in the EBSI registries (TIR, TSR).
+*The [https://wiki.de4a.eu/index.php/Authority_Agent Authority Agent] integrated into the [https://wiki.de4a.eu/index.php/EProcedure_Portal eProcedure Portal] validates the submitted VP in terms of the VC issuer (DP), holder (student) and the VC schema, and displays validation results. During the validation, the [https://wiki.de4a.eu/index.php/Authority_Agent Authority Agent] uses the integrated EBSI/eSSIF Connector to check the VP against entries in the EBSI registries (TIR, TSR).

← Older revision		Revision as of 12:21, 29 June 2021
Line 1:		Line 1:
−	~~Description of~~ the SA UC3 process	+	In MVP 1.0, the UC3 process flow includes the following steps:
		+	*A student accesses an [https://wiki.de4a.eu/index.php/Evidence_Portal] of a Data Provider (DP) to obtain a Verifiable Credential (VC).
		+	*The student is asked to authenticate at the DP using a legally recognized electronic identity (eIDAS identity).
		+	*After successful authentication, the student explicitly requests that he/she wants to obtain diploma evidence from the DP in the form of a Verifiable Credential.
		+	*If the DID connection between the student's [https://wiki.de4a.eu/index.php/User_Agent] (mobile wallet) and the [https://wiki.de4a.eu/index.php/Authority_Agent] integrated into the [https://wiki.de4a.eu/index.php/Evidence_Portal] has not yet been established, he/she requests a new QR code to be generated in order to establish the DID connection between two agents.
		+	*The student scans the QR code displayed in the [https://wiki.de4a.eu/index.php/Evidence_Portal] in his mobile wallet application and accepts the DID connection invitation.
		+	*Once the DID connection is established, the student requests the DP to send him his/her diploma evidence as a Verifiable Credential to his mobile wallet.
		+	*The DP retrieves the student's diploma from a registry, transforms it into a canonical format according to the [https://wiki.de4a.eu/index.php/SA_UC3_Data_Model] and to the JSON-LD format of a Verifiable Credential, digitally signs it with its DID key and sends it for preview on the student's mobile phone.
		+	*The student previews the Verifiable Credential offered by the DP and accepts the DP's VC offer.
		+	*The DP sends the final Verifiable Credential to the student who accepts the received VC and stores it under an arbitrary name in his/her mobile wallet for any future use.
		+	*A student then accesses an [https://wiki.de4a.eu/index.php/EProcedure_Portal] of a Data Consumer (DC) to submit a Verifiable Presentation (VP) for the required procedure.
		+	*The student is asked to authenticate at the DC using a legally recognized electronic identity (eIDAS identity).
		+	*After successful authentication, the student explicitly requests that he/she wants to submit diploma evidence to the DC in the form of a Verifiable Presentation.
		+	*If the DID connection between the student's [https://wiki.de4a.eu/index.php/User_Agent] (mobile wallet) and the [https://wiki.de4a.eu/index.php/Authority_Agent] integrated into the [https://wiki.de4a.eu/index.php/EProcedure_Portal] the has not yet been established, he/she requests a new QR code to be generated in order to establish the DID connection between two agents.
		+	*The student scans the QR code displayed in the [https://wiki.de4a.eu/index.php/EProcedure_Portal] in his mobile wallet application and accepts the DID connection invitation.
		+	*Once the DID connection is established, the student requests the DC to send him his/her a request for a VP submission.
		+	*The DC sends a request to the student containing information on the expected VP format to be submitted for procedural requirements.
		+	*The student accepts the received request on his/her mobile phone by selecting the requested VP conforming to the request format from his/her mobile wallet and submitting it as a response to the DC's request.
		+	*The DC receives and stores the VP submitted by the student under a specific name for any future references.
		+	*The student explicitly requests the DC to validate the submitted VP.
		+	*The [https://wiki.de4a.eu/index.php/Authority_Agent] integrated into the [https://wiki.de4a.eu/index.php/EProcedure_Portal] validates the submitted VP in terms of the VC issuer (DP), holder (student) and the VC schema, and displays validation results. During the validation, the [https://wiki.de4a.eu/index.php/Authority_Agent] uses the integrated EBSI/eSSIF Connector to check the VP against entries in the EBSI registries (TIR, TSR).