Difference between revisions of "Authority Agent"

From DE4A
Jump to navigation Jump to search
Line 13: Line 13:
 
| 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]]  
 
| [[VC]]  
 +
|-
 +
|Agent to Portal Connection
 +
|
 +
|
 +
|-
 +
|Agent to Agent  (Cloud)
 +
|
 +
|
 
|}
 
|}

Revision as of 12:05, 7 April 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 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.

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 record retrieval, its translation into the form of 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
Agent to Agent  (Cloud)