fix: require key-id when resolving key material #3655
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 changes the public key resolution, in that the
kid
is only required, if the DID contains multiple verification methods.Why it does that
Taking the first verification method if no
kid
is given is dangerous and wrong.Further notes
JwtPresentationVerifier
now uses theDidPublicKeyResolver
instead of theDidResolverRegistry
, which is better, because it limits the API surfaceLinked Issue(s)
Closes #3649
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.