Difference between revisions of "Authority Agent"

From DE4A
Jump to navigation Jump to search
m
 
(10 intermediate revisions by 4 users not shown)
Line 1: Line 1:
The Authority agent is responsible for managing the connections between User and authorities (i.e. DP, DC) and activities related to Verifiable Credentials/Presentations (i.e. proof requests, validation, issuing). To do so, it includes collaboration between several application components. The Verifiable Credential Generator reads the original evidence record on the DP side to generate and digitally sign the VC. This component is used by the SSI cloud agent, which is also responsible for managing the DID invitations to the User and providing interfaces for the communication between the Agent (cloud or edge) and the Evidence portal or the Ledger necessary to issue or verify VC/VP.
+
The Authority agent is responsible for managing the connections between User and authorities (i.e. DP, DC) and activities related to Verifiable Credentials/Presentations (i.e. proof requests, validation, issuing). To do so, it includes collaboration between several application components. The Verifiable Credential Generator reads the original evidence record on the DP side to generate and digitally sign the VC. This component is used by the SSI cloud agent, which is also responsible for managing the DID connections wiith the Users' edge agents and providing interfaces for the communication between the Agent (cloud or edge) and the Evidence/eProcedure portal necessary to issue or verify VC/VP. The component also includes the EBSI Connector responsible for handling operations that require interaction with the EBSI/eSSIF services.
  
 
<gallery widths="400" caption="Graphic representations of the Authority Agent application collaboration">
 
<gallery widths="400" caption="Graphic representations of the Authority Agent application collaboration">
 
File:DE4A authority agent.png|alt=Graphic representation of the Authority Agent application collaboration|[[Verifiable_Credentials_Pattern|VC]]
 
File:DE4A authority agent.png|alt=Graphic representation of the Authority Agent application collaboration|[[Verifiable_Credentials_Pattern|VC]]
 
</gallery>
 
</gallery>
 
+
[[File:BPMN SSI-AuthorityAgent v0.22.png|alt=Process flow for using the Authority Agent on the DP side.|thumb|400x400px|Process flow for using the Authority Agent on the DP side.]]
 
{| class="wikitable"
 
{| class="wikitable"
|+ Application Components of the Authority Agent
+
|+Application Components of the Authority Agent
 
|-
 
|-
! Application Component !! Description !! Pattern(s)
+
!Application Component!!Description!! Pattern(s)
 
|-
 
|-
| [[Verifiable Credential Generator]]  
+
|[[Verifiable Credential Generator]]
| Application component managing the generation, i.e., issuance of VC by the DP as issuer to the user as the holder of the newly generated (i.e., re-issued) evidence (VC). The component also includes the processes of evidence record retrieval, its translation into the form of VC, and the digital signing by the issuer of the evidence.
+
|Application component managing the generation, i.e., issuance of VC by the DP as issuer to the user as the holder of the newly generated (i.e., re-issued) evidence (VC). The component also includes the processes of evidence translation into the form of a VC and the digital signing by the issuer of the evidence.
| [[VC]]  
+
|[[Verifiable Credentials Pattern|VC]]
 
|-
 
|-
| [[SSI Cloud Agent Back-end|SSI Authority Agent Back-end]]
+
|[[SSI Cloud Agent Back-end]]
| Application component managing the DID connections and handling the VC/VP related events.
+
|Application component managing the DID connections and handling the VC/VP related events.
| [[VC]]  
+
|[[Verifiable Credentials Pattern|VC]]
 
|-
 
|-
 
|[[Agent to Portal Connection]]
 
|[[Agent to Portal Connection]]
|
+
|This interface provides two main functions to Evidence Portals and the eProcedure portal:
|[[VC]]
+
 
 +
#The creation of a DID connection requires a DID Invitation Object from the Agent to be displayed as a QR Code in the Portals (both Evidence and eProcedure)
 +
#For the Evidence Portal, this interface is able to receive an Evidence Record that is then transformed into a VC by the Verifiable Credential Generator of the Authority Agent.
 +
|[[Verifiable Credentials Pattern|VC]]
 
|-
 
|-
 
|[[Agent to Agent  (Cloud)]]
 
|[[Agent to Agent  (Cloud)]]
|
+
|Interface between Agents that provides the functionalities of a DID connection, e.g.: exchange of DID documents, Verifiable Credentials and Verifiable Presentations
|[[VC]]
+
|[[Verifiable Credentials Pattern|VC]]
 
|}
 
|}

Latest revision as of 10:32, 12 November 2021

The Authority agent is responsible for managing the connections between User and authorities (i.e. DP, DC) and activities related to Verifiable Credentials/Presentations (i.e. proof requests, validation, issuing). To do so, it includes collaboration between several application components. The Verifiable Credential Generator reads the original evidence record on the DP side to generate and digitally sign the VC. This component is used by the SSI cloud agent, which is also responsible for managing the DID connections wiith the Users' edge agents and providing interfaces for the communication between the Agent (cloud or edge) and the Evidence/eProcedure portal necessary to issue or verify VC/VP. The component also includes the EBSI Connector responsible for handling operations that require interaction with the EBSI/eSSIF services.

Process flow for using the Authority Agent on the DP side.
Process flow for using the Authority Agent on the DP side.
Application Components of the Authority Agent
Application Component Description Pattern(s)
Verifiable Credential Generator Application component managing the generation, i.e., issuance of VC by the DP as issuer to the user as the holder of the newly generated (i.e., re-issued) evidence (VC). The component also includes the processes of evidence translation into the form of a VC and the digital signing by the issuer of the evidence. VC
SSI Cloud Agent Back-end Application component managing the DID connections and handling the VC/VP related events. VC
Agent to Portal Connection This interface provides two main functions to Evidence Portals and the eProcedure portal:
  1. The creation of a DID connection requires a DID Invitation Object from the Agent to be displayed as a QR Code in the Portals (both Evidence and eProcedure)
  2. For the Evidence Portal, this interface is able to receive an Evidence Record that is then transformed into a VC by the Verifiable Credential Generator of the Authority Agent.
VC
Agent to Agent  (Cloud) Interface between Agents that provides the functionalities of a DID connection, e.g.: exchange of DID documents, Verifiable Credentials and Verifiable Presentations VC