fix: tweak the format of the verifiable credential JWT #3614
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 PR implements the following tweaks to the format of the JWT:
exp
claim.nbf
claim in addition toiat
(OK if these are the same)sub
would have to be thedid:jwk
value. But it's OK to have the realsub
if it's insidecredentialSubject
.aud
claim should be deleted, since it represents the intended verifier, not the client to whom the VC is issued. (An important difference from normal OIDC is that these are different!) In the Webex case, it's OK, since the app issuing the VC is the same as the app verifying it. But that's not true in general.email
,email_verified
,updated_at
) should be insidevc.credentialSubject
.For reference, an example JWT VC looks like this:
which decodes to the following claims: