feat: relying-party creates SI token for VP query #3659
Merged
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
This PR extends the
IdentityAndTrustService
and generates another SI token on the relying-party sidewhich is then used to execute the VP query against the counter-party's CredentialService (= presentation endpoint).
Why it does that
Complete the circle of the presentation flow
Further notes
access_token
to get thescope
string. This is a workaround, until we can extract the scope from the verification context. This behaviour will change in subsequent developments and is only there for the immediate future. The related code has been marked accordingly.access_token
constant was renamed toPRESENTATION_ACCESS_TOKEN_CLAIM
and is now used everywhereAudienceResolver
object, which maps a DSP url to an audience, which can be used to resolve key materialLinked Issue(s)
Closes # <-- insert Issue number if one exists
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.