Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update authorization flow to reflect verification of VCs (#48) #22

Merged
merged 2 commits into from
Aug 16, 2022
Merged

Update authorization flow to reflect verification of VCs (#48) #22

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4b56cfe
Update authorization flow to reflect verification of VCs (#48)
marcgs Aug 9, 2022
47875cc
Add details on invalid Verifiable Presentations
marcgs Aug 11, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/developer/decision-records/2022-06-08-identity-hub/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,8 @@ Each participant in the dataspace will have a single [decentralized identifier](

During participant-to-participant communication via IDS REST, the request destination participant queries the Verifiable Presentations of the request originator participant. Access to resources is granted or denied according to the policies in place and the available Verifiable Presentations.

Verifiable Presentations are issued and signed by a trusted authority. Before applying any policies, participants access the public key of that trusted authority from its DID Document, and check that Verifiable Presentations are valid. Only valid Verifiable Presentations must be taken into account in policy evaluations. Participants are responsible for reacting to the presence of invalid Verifiable Presentations as they see fit.

paullatzelsperger marked this conversation as resolved.
Show resolved Hide resolved
![Authorization](authorization.png)

Note that complex IDS flows, such as negotiating a contract agreement, requires multiple IDS requests flowing back and forth between participants. In that case, participants will alternate in the flow above, and both participants require an Identity Hub.
Expand Down
Binary file modified docs/developer/decision-records/2022-06-08-identity-hub/authorization.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
7 changes: 7 additions & 0 deletions docs/developer/decision-records/2022-06-08-identity-hub/authorization.puml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,10 @@ end box
box "Participant B" #LightGreen
Participant "Participant B\nAPI" as B
end box
box "Authority" #LightYellow
Participant "Authority\nDID Document" as DA
end box


ParticipantA -> B ++: Request:\n - DID JWS
activate ParticipantA
Expand All @@ -17,6 +21,9 @@ group authorize request
B -> B: Verify JWS
B -> IDHUB ++: Get Verifiable Presentation
return Verifiable Presentation
B -> DA ++: Get issuer DID Document
return DID Document (contains public key)
B -> B: verify Verifiable Presentation JWS
B -> B: apply access policy
end
return response
Expand Down