search

GLEIF-IT / sally

Apache License 2.0
4 stars 4 forks source link

System Architecture #1

Open tsterker opened 2 years ago

tsterker commented 2 years ago

Work-in-progress diagram of the system architecture as I currently understand it.

image

Sketchboard (password vlei): https://sketchboard.me/bDk4S9V4zRr#/

Christoph-Gleif commented 2 years ago

@tsterker This looks like what I had in mind. I think we then want to add some details to the "vLEI Reporting API", e.g. data storage etc.

pfeairheller commented 1 year ago

To things to address here:

  1. Both credential presentation and revocation messages with be KERI EXN protocol messages, not a typical web REST API.
  2. The messages will be authenticated by the signatures applied to the EXN messages by the QVI that sends them. What GLEIF wants to do with that authentication data is up to the vLEI Reporting API.
tsterker commented 1 year ago

Both credential presentation and revocation messages with be KERI EXN protocol messages, not a typical web REST API.

@pfeairheller That's what I also understood.

Still, further I understood that Sally would

i.e.

flowchart TD
qvi[QVI]

subgraph sally[Sally]
  api["API"]
  keripy
end

qvi -->|"(1) present"| api
api -->|"(2) 202 Accepted"| qvi
api -.->|"(3) KERI EXN"| keripy