Add support for JPT credentials with Split-BBS #193
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
Member
Author
|
@gsiou If y'all want to use a submodule for |
dpk is not included as an explicit payload, so there is no need to expose metadata for decoding it as a claim from a payload.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 depends on (branch: unsupported-format) and #189. See here for the diff without the changes included in #189.
Also depends on:
JPT support is largely a hack based on the JWT protocols. Essentially, I've copied the JWT things and replaced as little as possible with JPT equivalents where necessary. JPTs reuse the JWT VC metadata, masquerade as JWTs in the DCQL parsers and so on. The two are surprisingly compatible. 🙂