Doc: Design to get claims before applying access policy (#10) #5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added ADR to get claims before applying access policy.
ouphi
changed the title
ouphi
changed the title
docs/developer/decision-records/2022-07-01-get-claims/README.md
Outdated
Show resolved
Hide resolved
docs/developer/decision-records/2022-07-01-get-claims/README.md
Outdated
Show resolved
Hide resolved
7 tasks
paullatzelsperger
approved these changes
Jul 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR changes/adds
Added ADR explaining how we will get the claims of a participant before applying access policies.
There is also an EDC issue to propose to change the CredentialsVerifier contract.
Why it does that
We need to get claims in order to apply access policy.
Downstream issue: agera-edc#23