SSI Authority Agent Database
| Item | Description |
|---|---|
| name | SSI Authority Agent Database |
| description | Application component, which stores the current status of requests generated by the SSI Authority Agent as well as the currently valid EBSI-compliant DID of the AA instance. |
| pattern | VC |
| application collaboration | Authority Agent |
Database structure
The figure below shows the Entity-Relationship (ER) diagram of the database. The ER stores data in four entities: the DID connection (entity DIDConn), Verifiable Credential status (entity VCStatus), Verifiable Presentation status (entity VPStatus), and the DID (entity DID is only used for storing the DID value).
The DIDConn entity stores information on the current status of the DID connection invitation generated by the HL Aries agent. The data includes information about the generated DIDs of the two Aries agents (cloud and edge), the raw JSON invitation and the current status of the DID connection.
The VCStatus entity stores information on the current status of the VC exchange between the cloud and the edge HL Aries agents. It includes the information on the PIID (Protocol Instance Identifier) obtained after initiating the VC exchange between the agents, the VC data in JSON format and the current status of the VC exchange (includes information on the VC offer exchange status).
The VPStatus entity stores information on the current status of the VP exchange between the cloud and the edge HL Aries agents. It includes the information on the PIID (Protocol Instance Identifier) obtained after initiating the VP exchange between the agents, the VP data in JSON format as well as the VP name as stored by the HL Aries cloud agent and the current status of the VP exchange (includes information on the VP request exchange status).
The DID entity includes information about the EBSI-compliant DID generated during the Authority Agent startup, which is then used to digitally sign the VC issued to the student.
