Verifiable Credential Issuance and Verifiable Presentation Consumption #68
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This will become the main addition in the new minor version, allowing for the issuing verifiable credentials according to a recent draft of OpenID4VCI and the consumption of verifiable presentations in a federation setting according to OpenID4VP. All of this will be implemented as Plugins and configurable through static configuration.
In this version, DIDs will not be supported, as well as most credential formats out there, focussing on JWK-Thumbprint-bound jwt_vc Verifiable Credentials.
Also note that you should not count on this being anywhere "standards"-compliant, as most of these "standards" are in fact rapidly changing drafts.