Authentication with DIDs and VC

[simibac]

I am trying to use the DIDs and VCs created with Veramo for authentication. I am wondering what the messages between the holder and the verifier look like. If I am correct, we should be able to create SDR and SDR responses with Veramo. However, I keep running into unhandled error with the Veramo CLI.

I am able to create an SDR with the default values as follows veramo sdr create:

? Issuer DID did:ethr:0x69fb362b8bcc73714072169e3bffb54a3bf0fe1c
? Subject DID
? Tag (threadId)
? Claim type name
? Reason We need this to comply with local law
? Is essential Yes
? Add accepted issuer? Yes
? Issuer DID did:ethr:0x69fb362b8bcc73714072169e3bffb54a3bf0fe1c
? URL https://uport.me
? Add another accepted issuer? No
? Add another claim? No
? Add profile credentials? No
? Send No
{
  claims: [
    {
      issuers: [
        {
          did: 'did:ethr:0x69fb362b8bcc73714072169e3bffb54a3bf0fe1c',
          url: 'https://uport.me'
        }
      ],
      essential: true,
      claimType: 'name',
      reason: 'We need this to comply with local law'
    }
  ],
  credentials: []
}
jwt: eyJ0eXAiOiJKV1QiLCJhbGciOiJFUzI1NkstUiJ9.eyJpYXQiOjE2MTQ4NDgxMzgsInR5cGUiOiJzZHIiLCJjbGFpbXMiOlt7Imlzc3VlcnMiOlt7ImRpZCI6ImRpZDpldGhyOjB4NjlmYjM2MmI4YmNjNzM3MTQwNzIxNjllM2JmZmI1NGEzYmYwZmUxYyIsInVybCI6Imh0dHBzOi8vdXBvcnQubWUifV0sImVzc2VudGlhbCI6dHJ1ZSwiY2xhaW1UeXBlIjoibmFtZSIsInJlYXNvbiI6IldlIG5lZWQgdGhpcyB0byBjb21wbHkgd2l0aCBsb2NhbCBsYXcifV0sImNyZWRlbnRpYWxzIjpbXSwiaXNzIjoiZGlkOmV0aHI6MHg2OWZiMzYyYjhiY2M3MzcxNDA3MjE2OWUzYmZmYjU0YTNiZjBmZTFjIn0.OoesYc1nZGB5LN6CWDXgfta6Er3_4oIjDZuqYc6fFtKCsmwLro85g-mejoGX2GKt2zNXJEWTTEQlPqzHKesoLgE

The VC that fulfils the request can be selected (during the veramo sdr respond-process) with the space bar and looks as follows:

{
  credentialSubject: {
    name: 'Alice',
    id: 'did:ethr:0x69fb362b8bcc73714072169e3bffb54a3bf0fe1c'
  },
  issuer: { id: 'did:ethr:0x69fb362b8bcc73714072169e3bffb54a3bf0fe1c' },
  type: [ 'VerifiableCredential', 'Profile' ],
  '@context': [ 'https://www.w3.org/2018/credentials/v1' ],
  issuanceDate: '2021-03-04T08:54:21.000Z',
  proof: {
    type: 'JwtProof2020',
    jwt: 'eyJ0eXAiOiJKV1QiLCJhbGciOiJFUzI1NksifQ.eyJ2YyI6eyJjcmVkZW50aWFsU3ViamVjdCI6eyJuYW1lIjoiQWxpY2UifSwiQGNvbnRleHQiOlsiaHR0cHM6Ly93d3cudzMub3JnLzIwMTgvY3JlZGVudGlhbHMvdjEiXSwidHlwZSI6WyJWZXJpZmlhYmxlQ3JlZGVudGlhbCIsIlByb2ZpbGUiXX0sInN1YiI6ImRpZDpldGhyOjB4NjlmYjM2MmI4YmNjNzM3MTQwNzIxNjllM2JmZmI1NGEzYmYwZmUxYyIsIm5iZiI6MTYxNDg0ODA2MSwiaXNzIjoiZGlkOmV0aHI6MHg2OWZiMzYyYjhiY2M3MzcxNDA3MjE2OWUzYmZmYjU0YTNiZjBmZTFjIn0.udZEvJDZoXg3upALyt8WSx_26DYf-MNzZt_RiSTvStZQvea550D_dPKFepagrRsPSEdT3EoOnx4walfisbQTuQ'
  }
}

Now I want to respond to this request with veramo sdr respond:

? Selective disclosure request less than a minute did:ethr..fe1c asking to share: name
? name (essential)We need this to comply with local law: Alice (VerifiableCredential,Profile) issued by: did:ethr:0x69fb362b8bcc73714072169e3bffb54a3bf0fe1c 2 minutes ago
(node:4437) UnhandledPromiseRejectionWarning: Error: [veramo:data-store:identifier-store] Get requires did or (alias and provider)
    at DIDStore.<anonymous> (/usr/local/lib/node_modules/@veramo/cli/node_modules/@veramo/data-store/build/identifier/did-store.js:38:23)
    at Generator.next (<anonymous>)
    at /usr/local/lib/node_modules/@veramo/cli/node_modules/@veramo/data-store/build/identifier/did-store.js:8:71
    at new Promise (<anonymous>)
    at __awaiter (/usr/local/lib/node_modules/@veramo/cli/node_modules/@veramo/data-store/build/identifier/did-store.js:4:12)
    at DIDStore.get (/usr/local/lib/node_modules/@veramo/cli/node_modules/@veramo/data-store/build/identifier/did-store.js:29:16)
    at DIDManager.<anonymous> (/usr/local/lib/node_modules/@veramo/cli/node_modules/@veramo/did-manager/build/id-manager.js:61:31)
    at Generator.next (<anonymous>)
    at /usr/local/lib/node_modules/@veramo/cli/node_modules/@veramo/did-manager/build/id-manager.js:8:71
    at new Promise (<anonymous>)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:4437) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
(node:4437) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Here are my questions:

1. What am I doing wrong with the SDR response?
2. What is the Tag or threadId of a SDR?
3. What are the intentions of the url when creating a SDR? Will enable the verifier to directly send the SDR to the holder?

[simibac]

I opened an issue for this #415

[jasheal]

Thanks. Will have a look today.

[simibac]

any updates on this?

[jasheal]

@simibac Sorry for delayed response! There doesn't appear to be an issue with the SDR request. We demoed it only last week internally. We are putting together a full tutorial around this and hopefully publish it this week on the website.

Any suggestions for what could be covered?

[simibac]

Thank you Jason. Looking forward for the tutorial to clear things up.