SA UC3 Process

In MVP 1.0, the UC3 process flow includes the following steps:

• A student accesses an 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 User Agent (mobile wallet) and the Authority Agent integrated into the 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 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 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 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 User Agent (mobile wallet) and the Authority Agent integrated into the 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 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 Authority Agent integrated into the 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 Authority Agent uses the integrated EBSI/eSSIF Connector to check the VP against entries in the EBSI registries (TIR, TSR).