SSI Cloud Agent Back-end - Revision history

Martina.sestak: Added EBSI Connector component.

2021-11-12T08:35:49Z

Added EBSI Connector component.

Martina.sestak: Added SSI Agent DB component.

2021-11-11T11:48:35Z

Added SSI Agent DB component.

Martina.sestak: Updated info on components and services.

2021-11-11T11:44:18Z

Updated info on components and services.

Martina.sestak at 09:28, 9 June 2021

2021-06-09T09:28:23Z

Ictu mavi.cristache: VC link

2021-05-31T18:10:43Z

VC link

Ictu mavi.cristache at 20:24, 12 April 2021

2021-04-12T20:24:27Z

Martina.sestak: Added links to HL Aries documentation websites.

2021-04-11T08:36:04Z

Added links to HL Aries documentation websites.

Martina.sestak: Added components for the Authority Agent collaboration.

2021-04-11T08:32:41Z

Added components for the Authority Agent collaboration.

Martina.sestak: Updated component's name.

2021-04-11T08:16:33Z

Updated component's name.

Martina.sestak: Updated application services for the Authority Agent.

2021-04-11T08:13:42Z

Updated application services for the Authority Agent.

@@ Line 59: / Line 59: @@
 |The component that exposes a set of methods as an interface to the Authority Agent's back-end functionalities.
 |-
-|SSI Authority Agent Database
+|[[SSI Authority Agent Database]]
 |[http://couchdb.apache.org/ CouchDB]
 |[[Use Case "Diploma/Certs/Studies/Professional Recognition" (SA UC3)]]
 |The component responsible for internally storing the current status of DID connections and VC/VP-related requests.
 |-
 | [[Hyperledger Aries Server]]

@@ Line 58: / Line 58: @@
 |[[Use Case "Diploma/Certs/Studies/Professional Recognition" (SA UC3)]]
 |The component that exposes a set of methods as an interface to the Authority Agent's back-end functionalities.
 |-
 | [[Hyperledger Aries Server]]

@@ Line 27: / Line 27: @@
 ! Application Service !! Description !! Pattern
 |-
-| [[DID Connection Invitation]]
+| DID Connection Invitation
 | Generic. The service generates and provides a JSON invitation (DID document) with which the different stakeholders (e.g., users) can start the process of DID connection establishment.
 | [[Verifiable Credentials Pattern|VC]]
 |-
-| [[DID Connection Response]]
+| DID Connection Response
 | Generic. The service validates and checks the user's response to the generated DID connection invitation. As a result of this action, information on the DID connection establishment is provided.
 | [[Verifiable Credentials Pattern|VC]]
 |-
-|[[VP Validation]]
+|VP Validation
-|The service performs an initial screening and validation of the VP submitted by the user with regard to its schema structure, eIDAS identity matching and the validity of the digital signature. The result of this action is the information on the validity of the VP submitted for the procedure.
+|The service performs an initial screening and validation of the VP submitted by the user with regard to its schema structure, issuer validity, eIDAS identity matching and the validity of the digital signature. The result of this action is the information on the validity of the VP submitted for the procedure.
 |[[Verifiable Credentials Pattern|VC]]
 |-
-|[[VP Request]]
+|VP Request
 |The service, dependant on procedural requirements, generates a request for evidence in the form of verifiable presentations (VPs). It requires evidences to be aligned with a specific VP format.
 |[[Verifiable Credentials Pattern|VC]]
 |-
-|[[VC Issuing]]
+|VC Issuing
-|The service provides functionalities related to (re)issuing of requested evidence in the form of a VC. The VC is issued through an established DID connection and accepted VC.
+|The service provides functionalities related to (re)issuing of requested evidence in the form of a VC. The VC is issued after an established DID connection and accepted VC offer.
 |[[Verifiable Credentials Pattern|VC]]
 |-
@@ Line 62: / Line 62: @@
 | [https://www.hyperledger.org/use/aries Hyperledger Aries]
 | [[Use Case "Diploma/Certs/Studies/Professional Recognition" (SA UC3)]]
+| The component deployed on the DP/DC premises, which handles all DID invitation requests and VC/VP-related requests.
 |-
 |[https://github.com/hyperledger/aries-framework-go/tree/main/docs/rest Hyperledger Aries REST API]
@@ Line 69: / Line 69: @@
 |The component that exposes a set of methods as an interface to the HL Aries Go functionalities (DID generation, sending VC offer/VC, accepting requests, etc.). The component is used by the SSI Authority Agent REST API to implement SSI funcionalities and communication between the Authority and Edge Agent.
 |-
 |-
 |}

@@ Line 60: / Line 60: @@
 |-
 | [[Hyperledger Aries Server]]
-| DE4A
+| [https://www.hyperledger.org/use/aries Hyperledger Aries]
 | [[Use Case "Diploma/Certs/Studies/Professional Recognition" (SA UC3)]]
+|
 |-
 |[https://github.com/hyperledger/aries-framework-go/tree/main/docs/rest Hyperledger Aries REST API]
-|DE4A
+|[https://www.hyperledger.org/use/aries Hyperledger Aries]
 |[[Use Case "Diploma/Certs/Studies/Professional Recognition" (SA UC3)]]
 |The component that exposes a set of methods as an interface to the HL Aries Go functionalities (DID generation, sending VC offer/VC, accepting requests, etc.). The component is used by the SSI Authority Agent REST API to implement SSI funcionalities and communication between the Authority and Edge Agent.
@@ Line 71: / Line 71: @@
 |-
 | [https://github.com/hyperledger/aries-framework-go/blob/main/docs/rest/agent_webhook.md Hyperledger Aries Webhooks]
-| DE4A
+| [https://www.hyperledger.org/use/aries Hyperledger Aries]
 | [[Use Case "Diploma/Certs/Studies/Professional Recognition" (SA UC3)]]
 | The component that enables an automatic detection of changes on the HL Aries server (e.g. user's acceptance of DID connection invitation, VC offer/VC request, etc.).

@@ Line 15: / Line 15: @@
 |-
 | pattern(s)
-| [[VC]]
+| [[Verifiable Credentials Pattern|VC]]
 |-
 |application collaboration
@@ Line 29: / Line 29: @@
 | [[DID Connection Invitation]]
 | Generic. The service generates and provides a JSON invitation (DID document) with which the different stakeholders (e.g., users) can start the process of DID connection establishment.
-| [[VC]]
+| [[Verifiable Credentials Pattern|VC]]
 |-
 | [[DID Connection Response]]
 | Generic. The service validates and checks the user's response to the generated DID connection invitation. As a result of this action, information on the DID connection establishment is provided.
-| [[VC]]
+| [[Verifiable Credentials Pattern|VC]]
 |-
 |[[VP Validation]]
 |The service performs an initial screening and validation of the VP submitted by the user with regard to its schema structure, eIDAS identity matching and the validity of the digital signature. The result of this action is the information on the validity of the VP submitted for the procedure.
-|VC
+|[[Verifiable Credentials Pattern|VC]]
 |-
 |[[VP Request]]
 |The service, dependant on procedural requirements, generates a request for evidence in the form of verifiable presentations (VPs). It requires evidences to be aligned with a specific VP format.
-|[[VC]]
+|[[Verifiable Credentials Pattern|VC]]
 |-
 |[[VC Issuing]]
 |The service provides functionalities related to (re)issuing of requested evidence in the form of a VC. The VC is issued through an established DID connection and accepted VC.
-|[[VC]]
+|[[Verifiable Credentials Pattern|VC]]
 |-
 |}

@@ Line 1: / Line 1: @@
 <div class="res-img">
-[[File:SSI cloud agent b-e.png |SSI Cloud Agent Back-end]]
+[[File:SSI cloud agent b-e.png |SSI Authority Agent Back-end]]
 </div>