Difference between revisions of "SA UC3 Components"
Jump to navigation
Jump to search
Line 4: | Line 4: | ||
== Common evidence exchange components == | == Common evidence exchange components == | ||
+ | {| class="wikitable" | ||
+ | |'''Component''' | ||
+ | |'''Role''' | ||
+ | |'''Short description of its use''' | ||
+ | |- | ||
+ | |SSI Authority agent | ||
+ | |Data Consumer/ Verifier and Data Provider/ Issuer | ||
+ | |The SSI Authority agent is a component responsible for implementing the SSI approach (manage DP/DC DID, control, issue and receive VC securely interacting with students’ edge agents) and integrating with EBSI/eSSIF infrastructure. It exposes a set of API endpoints that a DC/DP service calls in order to manage verifiable credentials and implement the VC pattern. | ||
+ | |- | ||
+ | |SSI Edge agent | ||
+ | |Evidence Holder | ||
+ | |Component for students (mobile SSI-Wallet) to manage issued Diplomas (receive them from Issuers as Verifiable Attestations and send them to Verifiers as Verifiable Presentations). | ||
+ | |} |
Revision as of 14:09, 6 May 2021
Back to main SA UC3 page
Common eIDAS components
Common evidence exchange components
Component | Role | Short description of its use |
SSI Authority agent | Data Consumer/ Verifier and Data Provider/ Issuer | The SSI Authority agent is a component responsible for implementing the SSI approach (manage DP/DC DID, control, issue and receive VC securely interacting with students’ edge agents) and integrating with EBSI/eSSIF infrastructure. It exposes a set of API endpoints that a DC/DP service calls in order to manage verifiable credentials and implement the VC pattern. |
SSI Edge agent | Evidence Holder | Component for students (mobile SSI-Wallet) to manage issued Diplomas (receive them from Issuers as Verifiable Attestations and send them to Verifiers as Verifiable Presentations). |