feat: upload holder credentials via HTTP API #141
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.
Description of change
This update allows users to send their credentials directly through the designated
POST /v0/holder/credentials
in JWT format.This update allows users to upload their own credentials directly to UniCore securely. With this change, users can add and manage credentials that weren’t originally issued by UniCore, making it easier to integrate and use a variety of credentials within the platform.
Example:
In a future improvement we should make sure that UniCore will/can validate the credential's schema and validity (related to #151)
Links to any relevant issues
n/a
How the change has been tested
Tested through updated Postman Collection (see
Add signed Holder Credential
request).Definition of Done checklist
Add an
x
to the boxes that are relevant to your changes.