Difference between revisions of "User Agent"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | + | The User Agent ''presented in Figure 30'' includes the collaboration between the SSI edge agent front-end and back-end components on the User side in order to manage incoming DID invitations, checking VCs issued to the User (acceptance or negation) or create VPs. It also provides an interface to communicate with the cloud Authority Agent. The User can manage his received VCs inside his Digital Wallet (i.e. store them, select VCs (VPs) which are to be sent to DC, etc.) by communicating with the SSI edge agent back-end. | |
{| class="wikitable" | {| class="wikitable" | ||
Revision as of 14:40, 22 March 2021
The User Agent presented in Figure 30 includes the collaboration between the SSI edge agent front-end and back-end components on the User side in order to manage incoming DID invitations, checking VCs issued to the User (acceptance or negation) or create VPs. It also provides an interface to communicate with the cloud Authority Agent. The User can manage his received VCs inside his Digital Wallet (i.e. store them, select VCs (VPs) which are to be sent to DC, etc.) by communicating with the SSI edge agent back-end.
| Application Component | Description | Pattern(s) |
|---|---|---|
| SSI Edge Agent Front-end | Component building UI and logic to handle DID connections and the VC/VP related events. | VC |
| SSI Edge Agent Back-end | Application component managing the DID connections and handling the VC/VP related events. | VC |