did-jwt-vc
Create and verify W3C Verifiable Credentials and Presentations in JWT format
Installation
npm install did-jwt-vc
Usage
Creating JWTs
Prerequisites
Create an Issuer
object to sign JWTs using, for example ethr-did
import { EthrDID } from 'ethr-did'
import { Issuer } from 'did-jwt-vc'
const issuer = new EthrDID({
identifier: '0xf1232f840f3ad7d23fcdaa84d6c66dac24efb198',
privateKey: 'd8b595680851765f38ea5405129244ba3cbad84467d190859f4c8b20c1ff6c75'
}) as Issuer
The Issuer
object must contain a did
attribute, an alg
property that is used in the JWT header and a signer
function to generate the signature.
Creating a Verifiable Credential
Specify a payload
matching the CredentialPayload
or JwtCredentialPayload
interfaces. Create a JWT by signing it
with the previously configured issuer
using the createVerifiableCredentialJwt
function:
import { JwtCredentialPayload, createVerifiableCredentialJwt } from 'did-jwt-vc'
const vcPayload: JwtCredentialPayload = {
sub: 'did:ethr:0x435df3eda57154cf8cf7926079881f2912f54db4',
nbf: 1562950282,
vc: {
'@context': ['https://www.w3.org/2018/credentials/v1'],
type: ['VerifiableCredential'],
credentialSubject: {
degree: {
type: 'BachelorDegree',
name: 'Baccalauréat en musiques numériques'
}
}
}
}
const vcJwt = await createVerifiableCredentialJwt(vcPayload, issuer)
console.log(vcJwt)
Creating a Verifiable Presentation
Specify a payload
matching the PresentationPayload
or JwtPresentationPayload
interfaces, including the VC JWTs to
be presented in the vp.verifiableCredential
array. Create a JWT by signing it with the previously configured issuer
using the createVerifiablePresentationJwt
function:
import { JwtPresentationPayload, createVerifiablePresentationJwt } from 'did-jwt-vc'
const vpPayload: JwtPresentationPayload = {
vp: {
'@context': ['https://www.w3.org/2018/credentials/v1'],
type: ['VerifiablePresentation'],
verifiableCredential: [vcJwt]
}
}
const vpJwt = await createVerifiablePresentationJwt(vpPayload, issuer)
console.log(vpJwt)
Verifying JWTs
Prerequisites
Create a Resolver
using did-resolver and register the
ethr-did-resolver. When verifying a JWT signed by a DID,
it is necessary to resolve its DID Document to check for keys that can validate the signature.
import { Resolver } from 'did-resolver'
import { getResolver } from 'ethr-did-resolver'
const providerConfig = {
rpcUrl: 'https://mainnet.infura.io/v3/<YOUR infura.io PROJECT ID>',
registry: '0xdca7ef03e98e0dc2b855be647c39abe984fcf21b'
}
const resolver = new Resolver(getResolver(providerConfig))
Verifying a Verifiable Credential
Pass in a VC JWT along with the resolver to verify using the verifyCredential
function:
import { verifyCredential } from 'did-jwt-vc'
const verifiedVC = await verifyCredential(vcJwt, resolver)
console.log(verifiedVC)
Verifying a Verifiable Presentation
Pass in a VP JWT along with the resolver to verify using the verifyPresentation
function:
import { verifyPresentation } from 'did-jwt-vc'
const verifiedVP = await verifyPresentation(vpJwt, resolver)
console.log(verifiedVP)
Notes on verification and proof properties
The result of the verification methods, when successful, also conveniently contain the decoded and parsed payloads, in a
format that closely matches the W3C data model for verifiable credentials and
presentations. This makes it easier to work with both credential encodings in the same system. This parsed payload also
shows a proof
property that lists the full JWT credential or presentation.
The JwtProof2020
is a synthetic proof type, usable for differentiating credentials by type. It is not a registered W3C
VC Data Model algorithm and should not be treated as such.
Also note that the @context
fields that appear in this parsed payload are the same as the ones in the incoming JWT.
This means that the parsed payload will probably not be suitable for an LD-processor.
Please see #54 for more information.