feat: add Authorization header to BDRS request #1206
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
adds a VerifiablePresentation containing the
MembershipCredential
to theAuthorization
header of a BDRS request.Specifically, assuming we're using JWT-VPs, this will add a header:
In order to do that, the
BdrsClient
requires access to theSecureTokenService
to create a self-issued ID token.That SI token is then used to execute a
PresentationQuery
request toCredentialService
, we "IATP ourselves".The CredentialService's URL is resolved via a config parameter, and as a fallback, is resolved from the DID document.
WHY
Securing the directory API of the BDRS server.
FURTHER NOTES
A similar PR will come for the BDRS Server, to verify the auth header.
Closes # <-- insert Issue number if one exists